Meeting workflows · Updated October 8, 2026

Wispr Flow Notetaker with ChatGPT and Claude: Access, Windows & Limits

Turn meeting notes into a follow-up, a decision check or a project brief. This guide separates speaking a prompt into an AI tool from connecting the meetings already recorded in Wispr Flow.

Official documentation: Wispr alongside an existing notetaker.

Voice dictation and meeting access solve different problems

To explain a task aloud, dictate into the AI tool’s text field. To use a previous meeting, connect the meeting source. Speaking a request does not, by itself, give the assistant the conversation you are referring to.

Consider “write the email we agreed on yesterday.” Without the source, the assistant may only have your new description of that agreement. A useful request names the meeting and asks for retrieval before drafting.

How to connect Wispr Flow to ChatGPT or Claude

Open Flow Settings → MCP and use the card for your AI client. Complete browser authorization with the account holding your notes. Wispr’s guide says email-and-password sign-ins cannot complete this authorization; use one of its supported federated sign-in methods.

Official documentation: Wispr alongside an existing notetaker.

ChatGPT: current setup on the web

OpenAI’s manual setup instructions use ChatGPT Plugins → plus button → Add custom MCP server. Enter the connection details, configure authentication, then install the resulting plugin. Workspace permissions and security restrictions apply.

Official documentation: OpenAI: connecting a custom MCP server.

Start with Wispr’s own client card. If your client requests a manual server address, copy the exact endpoint displayed in Flow’s MCP settings, without an added trailing slash. An ordinary website or referral landing page is not a connection endpoint.

Claude: activate it in the relevant conversation

Enable Wispr in Claude’s conversation controls after setup. On a work account, the integration can first require an owner to make it available. Test the chat where you actually intend to use the meeting source.

Official documentation: Wispr MCP connection and access limits.

Does Wispr MCP search full meeting transcripts?

Documented search matches titles, summaries and notes, not transcript text. Find the meeting first, then explicitly request its transcript when you need the wording. Long retrieved content can arrive in portions. A missing search match does not establish that a phrase was never spoken.

Official documentation: Wispr MCP connection and access limits.

Separate what the source says, what the assistant infers and what remains unresolved. For a quotation, ask for the relevant passage instead of treating a paraphrased summary as an exact quote.

Keep old meeting history accessible alongside Wispr

Wispr documents keeping an existing notetaker connected alongside Wispr in an AI client that supports both, then naming both sources in the request. This can help work across old and new histories.

Connecting two sources is not a completed data import. Test each connection independently. If one is unavailable, the assistant should identify the missing source rather than presenting a partial search as complete.

Official documentation: Wispr alongside an existing notetaker.

Does Wispr Flow Notetaker work on Windows?

Yes. Its recording guide lists Mac and Windows. Complete setup and check a captured meeting before testing retrieval. Account allowances, organization policies and agreements can restrict recording even on a supported computer.

Official documentation: Recording with Notetaker on Mac and Windows.

Does Notetaker support French or 100+ meeting languages?

French is in the dedicated 22-language Notetaker list checked October 8. The document also includes Hinglish and describes automatic meeting-language detection. The 100+ language claim belongs to dictation; its language preference does not select the meeting language.

Official documentation: Notetaker language support.

Make the first test representative: use the client names, acronyms and mixed-language discussion that appear in your real calls. A successful English demonstration does not validate a French client meeting.

A practical meeting-to-follow-up workflow

The benefit is turning a verified conversation into a draft with fewer missing details. Use this sequence for a client call or internal project review.

1. Identify the source. Name the meeting, participants and approximate date.
2. Retrieve before drafting. Ask for the available notes and a short account of the decisions.
3. Check commitments. Separate proposed actions from accepted actions; identify missing owners or deadlines.
4. Draft for the audience. Request an email, project brief or internal update using confirmed material.
5. Review before sending. Check names, numbers, promises and information that should stay internal.

Another useful task is comparing two project meetings. Ask what changed, which decision superseded an earlier one and which issues remain open. Have the assistant identify both meetings so you can assess whether the comparison covers the relevant period.

What changes when you connect meeting history?

Wispr describes account-wide authorization covering existing meetings, subject to access restrictions, rather than a separate approval for each recording. That is broader than pasting one chosen summary into a chat.

Official documentation: Wispr alongside an existing notetaker.

Bot-free capture still uses cloud processing

The privacy document says Notetaker captures microphone and system audio for cloud processing. Supported capture during a connection interruption can save audio locally for processing later. It is not a fully local transcription engine.

Retention differs by data type. Uploaded audio is normally removed seven days after upload, potentially sooner for some accounts. Transcripts can remain until a retention rule or deletion applies, while notes and summaries have separate lifetimes. An audio-deletion period is not a deletion period for every meeting record.

Official documentation: Notetaker processing and retention.

Audit scope and BAA restrictions

The security overview says Notetaker was not included in the audit periods covering dictation. It also says a signed HIPAA BAA blocks Notetaker recording. Check the covered product and account configuration before extending a dictation assurance to meeting recording.

Official documentation: Security overview and audit scope.

For transcripts, Wispr’s access guide requires ownership or an email invitation and the owner’s organization permitting transcript sharing. A shared summary link alone does not establish transcript access.

Official documentation: Transcript access requirements.

If a connected meeting does not appear

Start with one known recording. Verify that it is visible in the authorized account, then name it explicitly. This distinguishes “the connection cannot retrieve my meeting” from “a broad search did not match the detail I remembered.”

If a summary is accessible but its transcript is not, check permissions and retention. Reconnecting cannot recreate deleted content. If your organization requires a particular setting, follow the access explanation rather than repeatedly authorizing the same connection.

Who benefits from this workflow?

It is useful when meetings regularly turn into writing: consultants preparing follow-ups, founders reviewing decisions and project teams producing briefs. The value comes from retrieving and checking context.

If you only want to speak long prompts, start with dictation. If meeting history is the requirement, test retrieval of an actual recording on the account you plan to use.

Official sources checked

• Wispr MCP connection and access limits
• Using Wispr alongside an existing notetaker
• Recording on Mac and Windows
• Notetaker languages
• Notetaker processing and retention
• Security and audit scope
• OpenAI manual MCP connection guide

Product documentation checked October 8, 2026.