What's inside Pricing FAQ Blog Documentation Sign in →

Claude, answering from your own meetings

Claude is good at reasoning over material it has been given, and bad at knowing what you said on a call in March. The MCP connector closes that gap: Claude gets read access to the meetings you share, and the reasoning stays where it is good.

Connect Claude How access is controlled

Custom connector · consent per area · paid plans

Where to put the address
Claude → Settings → Connectors → Add custom connector

  URL        https://whisperer.one/mcp
  Client ID  (leave empty)

Claude registers itself, opens Whisperer in your
browser and shows the list of areas it is asking for.

Setup

Four steps, and the third one is the important one

  1. Check the plan

    MCP runs on Start, Pro and Max. On Free the server refuses with a subscription error, which looks like a broken connector but is not one.

  2. Add the connector

    Settings, then Connectors, then Add custom connector. Paste the address and leave the client ID empty — Claude registers itself.

  3. Read the consent screen

    Whisperer opens in your browser and lists exactly which areas Claude is requesting. Approve the ones it actually needs; you can reconnect later with a wider set.

  4. Share some meetings

    In your account, mark the calls Claude may read. Nothing is shared by default, so this step is what turns an empty list into answers.

In practice

What people actually ask it

The pattern that works is a question whose answer only exists in your own history — the kind Claude cannot bluff, and would otherwise answer generically.

Works wellQuestions with a source

  • Summarise everything we agreed with this client this quarter

    reads shared calls

  • Draft the follow-up from Tuesday's call, in my usual tone

    transcript plus notes

  • Which commitments have no owner yet

    meetings plus tasks

Will not workQuestions with no source

  • Delete the meetings from last month

    deletion is never exposed

  • Email this summary to the client

    cannot act in other services

  • What did we discuss before I started using Whisperer

    no such meeting exists

Limits

Two boundaries worth stating twice

  1. First Claude reads; it does not delete

    Deletion is not exposed through the server at all, so no approval and no instruction makes it available. Neither are your passwords or API keys, and neither is acting inside your other connected services.

  2. Second Only shared meetings, only approved areas

    Two independent gates. If Claude returns nothing, one of them is closed — most often the sharing one, because nothing is shared by default.

Questions

Claude connector questions

What can Claude access through Whisperer MCP?

The meetings you marked as shared and their transcripts, plus your tasks, calendar, files, knowledge base, prompts and support tickets — each only if you approved that area on connection.

Does this send my meetings to Anthropic?

Claude reads what you asked it to read, in order to answer you — the same way it reads a file you attach to a message. The scope is what you shared and what you approved; nothing is transferred in the background.

Can I revoke it later?

Yes, in your Whisperer account, and it takes effect immediately. Giving the connection a recognisable name in Claude makes it obvious which one to revoke.

Do I need to approve every area?

No, and it is better not to. Approve what the client actually needs; reconnecting later with a wider set takes a few seconds.

Claude connected, but sees no meetings.

Nothing is shared by default. Mark the meetings you want it to read in your account, and the same question will start returning them.

Try it with one meeting

Share a single call, then ask Claude what was decided in it. Either the answer contains specifics only that call could supply, or something upstream is not set up yet.

Start free

Related pages