Give Claude, ChatGPT and Cursor your meetings
MCP is an open standard for letting an AI client work with your data in another service. Whisperer runs a server for it, so the assistant you already use can answer from your own calls instead of from general knowledge — without you pasting anything.
Paid plans · consent per area · nothing shared by default
{
"mcpServers": {
"whisperer": { "url": "https://whisperer.one/mcp" }
}
}
Two gates
Nothing is visible until you make it visible
There are two separate switches, and both must be on before an external client sees anything. This is deliberate: a connector that reads everything by default is one accidental approval away from handing your entire history to a tool you were trialling.
- Gate one Which meetings You mark the individual meetings an external client may read. An empty result usually means nothing has been marked yet, not that the connection failed.
- Gate two Which areas On connection you see exactly which areas the client is asking for — meetings, tasks, calendar, files, knowledge base — and approve them one by one.
Boundaries
What an external client can never do
These limits live in the server, not in a settings page, which means no approval you click and no instruction the client is given can widen them.
- Delete anything
- Receive your passwords or API keys
- Act inside your other connected services
- Send mail as you, post to your chat, write to your CRM
- Read the meetings you shared and search their transcripts
- Work with your tasks and calendar
- Read files, notes and prompts
- Open and follow your support tickets
Clients
Three that people connect first
The server is the same in every case; the setup path differs because each client handles connectors its own way.
Limits
Two limits to know before connecting
MCP works on Start, Pro and Max. On Free the server answers with a subscription-required error, which is the most common reason a first connection appears to fail.
MCP exposes the meetings that exist, and meetings exist because Whisperer was running during them. It is not a way to bring an archive of old recordings into Claude.
Questions
What people ask first
What is the Whisperer MCP server?
An endpoint at https://whisperer.one/mcp that speaks the Model Context Protocol. Any MCP-capable client can connect to it and, within the areas you approve, read your meetings and work with your tasks, calendar and files.
How is access controlled?
By two things at once: the meetings you explicitly marked as shared, and the areas you approved on the consent screen. Revoking a connection in your account takes effect immediately.
Can I use a personal token instead of the browser flow?
A personal token opens the shared meetings for reading only. Full access, including tasks and calendar, goes through the consent flow in the browser.
The client returns an empty list. What is wrong?
Usually nothing. Nothing is shared by default, so an empty list means no meeting has been marked visible yet. The other common cause is being on the Free plan.
Does this work with clients other than these three?
Any MCP-capable client can connect. Those that read a config file use the JSON above; those with a connector interface take the address directly, leaving the client ID empty.
Share one meeting and ask about it
That is the whole trial: mark a single call as visible, connect the client, and ask it what was decided. If it answers, everything else is a matter of scope.