Skip to main content
Connect OpenWhispr to an AI assistant and you can ask about anything you’ve said or recorded, without copying and pasting. The assistant looks it up in your OpenWhispr account, answers, and can save the result back as a note. This page starts with Claude. The same connection works in other assistants that support MCP — the standard way AI apps connect to other services — such as ChatGPT and Cursor.

​
What you can ask

Once you’re connected, try questions like these:
  • “What did we decide about pricing in Tuesday’s design review?”
  • “Pull the action items out of my last three meeting notes.”
  • “Turn the transcript of my call with Priya into a follow-up email.”
  • “What have I been dictating about the launch plan this week?”
  • “Summarise today’s meetings and save the summary as a note in my Weekly folder.”
  • “Add Siobhán, Kubernetes and SOC 2 to my dictionary.”
  • “Make a snippet so ‘cal link’ becomes my booking URL.”
  • “How many words have I dictated this month?”
Your assistant can reach:
  • Your notes and folders — read, search, create, edit and organise them.
  • Meeting transcripts — who said what, with timestamps.
  • Your dictation history — what you’ve dictated, and when.
  • Your dictionary and snippets — the words OpenWhispr should always spell right, and the phrases that expand into longer text.
  • Your usage and plan — word counts and plan details.

​
Before you start

Your assistant reads the copy of your OpenWhispr data that’s backed up to your account, not the copy on your computer. So two things need to be true:
  1. You’re on a paid plan, and
  2. Cloud backup is on: Settings, then Privacy & Data under System.
Cloud backup is off by default. Until it’s on, your assistant finds little or nothing, and notes it creates won’t reach the app. See sync notes across devices for what it backs up.

​
Claude on the web or desktop

Any Claude plan can add OpenWhispr — the Free plan allows one custom connector — but on Team and Enterprise plans an Owner has to add it first. See below.
1

Open Connectors

In Claude, go to Customize, then Connectors. In the desktop app, Customize is in the sidebar.
2

Add OpenWhispr

Click Add custom connector. Enter the server URL:
Give it the name OpenWhispr and click Add. You don’t need an OAuth client ID or secret — leave those settings as they are.
3

Sign in to OpenWhispr

Click Connect on the new connector if Claude doesn’t open the sign-in page for you. On Sign in to connect, sign in the same way you sign in to the desktop app — Google, Microsoft, Apple, email, or single sign-on.On claude.ai the page opens in the same tab. In the desktop app it opens in your browser.
4

Approve access

The next screen reads Claude wants to connect to OpenWhispr. Check that the email under OpenWhispr account is the account you use in the app, then click Connect to Claude. You’re sent back to Claude, and OpenWhispr shows as Connected.
5

Turn it on in a chat

In a conversation, click + in the message box, choose Connectors, and make sure OpenWhispr is switched on. Then ask away.
Once connected, OpenWhispr also works in the Claude mobile app, and in Claude Code when you’re signed in there with the same Claude account.
When OpenWhispr appears in Claude’s connector directory, you’ll also be able to find it under Customize → Connectors → Discover and click Connect to Claude. The sign-in and approval steps are the same.

​
On a Claude Team or Enterprise plan

Members usually can’t add a custom connector themselves. An Owner adds OpenWhispr once for the whole organisation:
  1. Go to Organization settings, then Connectors.
  2. Click Add, then Custom. If Claude asks for the type, choose Web.
  3. Enter https://mcp.openwhispr.com/mcp and click Add.
Each member then goes to Customize → Connectors, finds OpenWhispr with the Custom label, and clicks Connect to sign in with their own OpenWhispr account. Everyone only ever sees their own notes.

​
Choose when Claude asks first

Claude sorts OpenWhispr’s tools into read-only tools and write/delete tools, and you decide how each group behaves. Open Customize → Connectors → OpenWhispr and, under Tool permissions, choose Always allow, Needs approval, or Blocked for each group or for a single tool.
  • Keep write/delete tools on Needs approval and Claude stops to ask before it creates, edits or deletes anything. Choose Allow once to let that one action through.
  • Set them to Blocked to keep the connection read-only.
If you click Always allow on a write tool, Claude stops asking for that tool. Do that only for tools you’re comfortable letting it run on its own — Delete note in particular.

​
Claude Code

Run this in your terminal:
Then sign in:
Or, inside Claude Code, type /mcp, choose openwhispr, and follow the prompt to sign in. Either way your browser opens the same OpenWhispr sign-in and approval pages as above; when you’re done, head back to the terminal. Add --scope user after --transport http to make OpenWhispr available in every project, not just the folder you’re in.

​
Other AI tools

Any app that supports remote MCP servers can use the same address, https://mcp.openwhispr.com/mcp — ChatGPT and Cursor, for example. If the app supports signing in (OAuth), you’ll see the same OpenWhispr sign-in and approval pages. If an app can only send a fixed key instead, use an API key:
  1. In the OpenWhispr desktop app, click Integrations in the sidebar, then API keys.
  2. Click Create API Key, name it after the app, tick only the permissions it needs, and choose when it expires.
  3. Copy the key — it starts with owk_live_ and is shown only once — and give it to the app as the header Authorization: Bearer followed by the key.
API keys are on paid plans. Setup for Cursor, VS Code and other developer tools is in MCP server, and everything about keys is in API keys.

​
What your assistant can and can’t do

Your assistant can only do what these tools allow. The ones on the right change something in your account; the rest only read. A few things worth knowing:
  • Notes your assistant creates or edits land in your account, and reach the desktop app the next time it syncs.
  • Search covers your notes. For dictation history, the assistant reads through the list instead, so a narrow question — a topic, a day — gets a better answer.
  • It sees your personal notes. Notes in team spaces aren’t included.
  • Transcribe audio turns a short clip (up to 3 MB) into text with OpenWhispr Cloud. It’s in beta, needs a Pro or Business plan, and uses your 600 monthly API transcription minutes. It doesn’t change anything you’ve saved, but because it isn’t read-only, Claude lists it with the tools that change data.
  • It can’t change your OpenWhispr settings or plan, see your API keys, read other people’s notes, or see anything that’s only on your computer.

​
Privacy and disconnecting

  • Your assistant sees only what your account can see. It signs in as you, so it reaches your own data and nobody else’s. The approval screen lists what it can do; the list is the same for every connection, so use your assistant’s own tool settings — in Claude, Tool permissions — to narrow it.
  • It uses OpenWhispr only when you ask. In Claude, it reaches in only in conversations where the connector is switched on, to answer what you’ve asked.
  • What your assistant reads becomes part of that conversation, which the company behind the assistant handles under its own terms and privacy policy — Anthropic, for Claude. OpenWhispr’s connection passes requests through and doesn’t keep a copy. If you work with health information, read HIPAA and healthcare before connecting.
  • It doesn’t use up an API key. Signing in this way doesn’t count towards your five personal API keys.
  • It stays connected while you use it. If you don’t use it for 30 days, you’ll be asked to sign in again.
To disconnect:
  • Claude on the web or desktop: Customize → Connectors → OpenWhispr, then Disconnect. To remove it completely, use the three-dot menu and choose Remove. On Team and Enterprise plans, an Owner removes it for everyone from Organization settings → Connectors.
  • Claude Code: run claude mcp logout openwhispr to sign out, or claude mcp remove openwhispr to remove it completely.
  • An app using an API key: in the desktop app, open Integrations → API keys and click the bin icon beside the key, then Revoke. Anything using that key stops working straight away.
Read our Privacy Policy for how OpenWhispr handles your data.

​
Troubleshooting

Disconnect and reconnect. Go to Customize → Connectors → OpenWhispr, click Disconnect, then Connect and sign in again.Also check the chat itself: click + → Connectors and make sure OpenWhispr is switched on.
Check Cloud backup is on in Settings → Privacy & Data, and that you’re on a paid plan. Your assistant reads what’s backed up to your account, so anything that’s only on your computer is invisible to it. Notes in team spaces aren’t included either.If backup is on and it still finds nothing, you may have connected a different OpenWhispr account — see the next question.
Disconnect, then connect again. In Claude, that’s Customize → Connectors → OpenWhispr → Disconnect, then Connect. On the approval screen, click Not you? Switch account under the email address, sign in with the right account, and approve.
You’re on a Claude Team or Enterprise plan, where connectors are usually added by an Owner. Ask an Owner to add OpenWhispr for your organisation — the steps are above — then connect your own account.
The sign-in page waits about 10 minutes. Go back to your assistant and start connecting again.
Claude has lost access, usually because the connector went unused for 30 days. Click Reconnect and sign in again.