Connect Claude, ChatGPT or another MCP client to Wispr Flow

Last updated: October 30, 2026

Available on: Mac and Windows. Requires Notetaker and MCP access on your Wispr Flow account.

Use an MCP-compatible AI app to search your Notetaker meetings without manually copying transcripts. Access is read-only: clients cannot create, edit, share or delete content, change sharing settings, or read dictation history or Notetaker chat history.

Before connecting

Account: Personal and work accounts have separate content, so authorize the correct Wispr Flow account in your browser.
Cloud access: If Flow prompts you to enable Dictation cloud storage, follow the prompt if it is unlocked; HIPAA and organization policies override your toggle. If Notetaker works with cloud storage off, meeting and calendar requests use that same access over MCP.
Organization policies: Notetaker, cloud access and MCP are separate controls; enabling one does not override the others. MCP is on by default, and solo accounts have no organization MCP policy. Turning MCP off blocks every MCP feature, including for already-authorized clients, without hiding existing meeting data in Flow; it stops Wispr using connected-service permissions but does not revoke those permissions with the provider.
HIPAA: An active personal or organization BAA blocks every MCP feature and removes Wispr tools from the client's available tools, regardless of cloud storage. Review managing a signed BAA with the account owner or admin. Revoking one agreement lifts only that agreement's restriction, not an organization's separate BAA. Organization BAAs are managed in the admin portal, not the desktop app; the desktop personal-revoke control is available only to solo accounts.

Connect your client

Note: With Google, Apple, Microsoft or enterprise SSO sign-in, finish browser sign-in within 5 minutes. With email-and-password sign-in, the login page must return you to authorization to finish connecting; signing in alone does not confirm setup. Authorization is account-wide and includes existing content, with no per-meeting consent and no API key or token.

Open Wispr Flow Settings → MCP.

Claude, ChatGPT, Gemini or Cursor

Choose Add to Claude, Add to ChatGPT, Add to Gemini or Add to Cursor. The buttons open setup pages in your default browser: Claude, ChatGPT, gemini.google.com/apps, or the Wispr Flow listing on the Cursor marketplace.

On a Claude Team or Enterprise plan, an Owner may need to add the connector for the organization first; then connect from Claude's Settings → Connectors.

Another MCP client

Flow shows a read-only Server URL for other MCP clients.

Copy the URL under All other apps: by clicking the field or Copy server URL. If you see “Couldn't copy the URL. Try again.”, retry copying.
Add the URL as a remote MCP server in your client, exactly as shown, without a trailing slash. Look under Settings → Connectors, Plugins or Customize, or follow the client's documentation.

Authorize and test

Sign in with your Wispr Flow account and authorize access in the browser.
Confirm Wispr Flow appears as authorized in your client's MCP server or connector list.
In Claude, enable Wispr Flow for the conversation with the chat box's + → Connectors → Wispr Flow toggle.
Start a chat and ask about a recent meeting. If the answer refers to your actual meetings, you're connected; otherwise use the recovery steps below.

What the connection can read

Clients can read meeting summaries, notes, transcripts and attendees; calendar events and linked recordings; upcoming meetings; recurring meetings; and shared-note links you can access. They can also resolve calendar or conference links to events.

Speaker names you corrected or linked to a contact in Notetaker are used over MCP too, so transcripts, summaries, notes, participant lists and search excerpts show those names instead of "Speaker 1". On meetings shared with you, speakers the owner linked to their private contacts are not named.

Questions phrased in the first person — "what did I commit to", "my meetings" — are answered directly: your name and the names you appear under in calendar invitations are shared with the client when it connects, so no separate identity lookup is needed. Your identity is not shared with HIPAA-covered accounts or organizations that have turned MCP off.

Meeting search covers meetings you own and notes shared with you, in one list, newest-modified first. Shared notes match on title and summary only — the owner's private notes, transcript text and hidden mention or citation data are never searched — and each shared result names the owner, is marked as shared, and indicates whether you may read its transcript. Date and attendee filters on a shared note use your own copy of the calendar event. Searching by contact or person, and follow-up requests such as a meeting's participants or a recurring series, cover your own meetings only.

Shared links still require your own meeting-access permissions. Transcripts require ownership or an email invitation, plus the owner's organization allowing transcript sharing; domain/team or anyone-with-link access gives summaries only.

Warning: Transcript retention starts when you or your organization selects a period; it deletes transcripts and audio, not summaries or My Notes. Completed audio has a separate default retention period of 7 days from successful upload. Deleted transcripts are unavailable through MCP and cannot be restored from an offline device. Deleting a meeting is permanent; MCP cannot restore it. See meeting-data retention.

Manage connections

Clients read from your Flow account, so Flow does not need to stay open. The same Server URL works with multiple clients; authorize each separately in the browser.

After a client connects, its card replaces Add to… with … → Reconnect, which reopens setup. Cards reflect past setup, not current access: OpenAI clients including Codex share the ChatGPT card, other custom clients may connect without changing a card, and a card can return to Add to… without proving disconnection. To refresh the cards, return to Flow; if they are unchanged, wait 30 seconds and refocus the window. Offline or failed checks keep the last displayed state.

To disconnect a client, remove Wispr Flow in that client's connector settings; Flow has no disconnect control. Changes to MCP, Notetaker, HIPAA or cloud access—including revoking a BAA—can take a few minutes to apply.

Fix connection or missing-note problems

Connected, but no matching notes

Search matches titles, summaries and your own notes, not transcripts. Attendee-email filters only find recordings linked to calendar events, and results show a short summary or notes excerpt and up to five attendees, not the full meeting content.

Check the authorized account, cloud access and the connector's per-chat toggle.
Ask again naming a specific meeting or date, narrowing the request if results are cut off.
Request full meeting details or the transcript explicitly. Clients read a full transcript in portions when asked, and long notes also arrive in portions, while summaries are complete.

If the answer identifies the intended meeting, the connection works; otherwise check the errors below.

Meetings recorded while cloud storage was off can remain missing after re-enabling it. An unrecorded calendar event returns its title and time without recording content, and "no earlier occurrence" can mean a one-off meeting or a recording with no linked calendar event — not a connection failure. For a past event, ask for its recording rather than an upcoming meeting.

If a shared-note link copied from email is rejected, open it in a browser and paste the final Wispr Flow URL.

Calendar events missing from answers

A calendar needing reauthorization hides only that provider's events, attendees and meeting times — Google reauthorization does not hide Outlook events — and deletes nothing; meeting notes and recordings stay available.

Warning: Disconnecting or switching calendar accounts removes Flow's copies of events not linked to recordings; meeting-linked events are retained.

Open Wispr Flow Settings → Connectors.
Choose Reconnect for the affected calendar, or Finish connecting if permission approval is incomplete.
Complete browser authorization. If prompted to disconnect the existing account first, do so and repeat these steps.
Ask again in your client; the provider's calendar data reappears automatically. Events never added during the interruption need time to appear, so completion is not necessarily immediate.

Admin-approval or policy restrictions require your admin's help.

Connection cancelled or authorization error

Expired access prompts reconnection, and an expired or failed setup attempt can end at the dashboard without connecting.

Connect again from the client and approve access in the browser.
Repeat the recent-meeting test. If it fails, check the client's connector settings for the exact error.

An organization turning Notetaker off blocks new recordings, not existing MCP reads; other access policies and retention still apply.

What you see	What to do
“Cloud Sync must be enabled to use this feature.”	Enable it if unlocked; otherwise request access and contact your admin, since requests do not change policy.
“This feature is not available for HIPAA-covered accounts.”	Review the BAA guidance under Before connecting.
“MCP access has been disabled by your organization's administrator.”	Ask your admin to check MCP and Notetaker access.
Meeting or calendar event not found	Confirm the authorized account, then ask again naming the meeting or date.
Too many requests	Pause repeated queries, wait about a minute, then retry.
Enterprise IP-allowlist denial	Connect from an approved network or contact your admin, then retry.

Service can be temporarily unavailable without your exceeding a limit, and other tools may still work; try again later, then repeat the meeting test.

Still need help?

Contact support if the meeting test still fails, if an error says retrying with the same inputs will not help, or if your account is banned or deleted.

Choose Report an issue, not Share feedback.
Select Issue as the Request Type.
Include the AI client, platform and device, the failing step, the exact error and what you tried.

A message is required and must stay within 10,000 characters; you can attach one image up to 10 MB. If sending fails, Flow copies your message to the clipboard so you can paste it and try again.