MCP: connecting Claude, ChatGPT and Cursor

Overview

MCP (Model Context Protocol) is an open standard that lets an external AI client work with your data in another service. Whisperer runs an MCP server, so Claude, ChatGPT, Cursor and any other MCP-capable client can read your meetings and act on your tasks, calendar and files — without you copying anything by hand.

The server address is https://whisperer.one/mcp. Access requires an active paid plan and your explicit consent: on connection you see a screen listing exactly which areas the client is asking for, and you approve or refuse them.

When to use it

  • You work in Claude or ChatGPT and want them to answer from your own meetings instead of general knowledge.
  • You write code in Cursor and want the assistant to see the decisions made on the call.
  • You want an external assistant to create tasks or calendar events for you without leaving its window.

Step-by-step

  1. Check your plan. MCP works on Start, Pro and Max. On Free the server answers subscription_required.
  2. Open your client's connector settings. In Claude it is Settings → Connectors → Add custom connector; in ChatGPT it is the connectors section. Cursor and similar tools read a config file instead — see step 4.
  3. Enter the address https://whisperer.one/mcp and leave the client ID empty. The client registers itself, opens Whisperer in your browser, and shows a consent screen with the list of areas it requests. Approve the ones you want.
  4. For a config-file client, add the server to its configuration:
    {
  "mcpServers": {
    "whisperer": { "url": "https://whisperer.one/mcp" }
  }
}
  5. Choose which meetings are visible. In your account, mark the meetings you want the external client to read. Nothing is shared by default.
  6. Check it worked. Ask the client to list your meetings. If it returns them, the connection is live.

What the external client can and cannot do

It can read the meetings you shared, search transcripts, and work with your tasks, calendar, files, knowledge base, prompts and support tickets — within the areas you approved.

It can never delete anything, never receive your passwords or API keys, and never act inside your other connected services: it cannot send mail from your address, post to your chat, or write to your CRM. Those limits are part of the server and no setting turns them off.

Common mistakes

  • Expecting all meetings to be visible. Only the ones you explicitly marked as shared are readable. An empty list usually means nothing has been shared yet.
  • Using a personal token to call tools. A personal token from your account only opens shared meetings for reading. Full access goes through the browser consent flow.
  • Connecting on Free. The server refuses with subscription_required; upgrade to a paid plan first.
  • Approving every area out of habit. Approve what the client actually needs — you can reconnect later with a wider set.

Best practices

  • Share the specific meetings a client needs, not the whole archive.
  • Give the connection a recognisable name in your client so you know which one to revoke later.
  • Revoke access in your Whisperer account when you stop using a client — revocation takes effect immediately.

Related articles