Claude Wispr Flow connectorWhat Claude can do in your Wispr Flow account.
The Claude Wispr Flow connector exposes 16 tools: 14 read tools, 2 write tools. Most reread your meetings, notes and calendar; two handle your tasks. Below: what Claude can find, what blocks sign-in, and where the publisher's own pages disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes after a week full of meetings
Wispr Flow records your meetings and keeps their transcripts, your Scratchpad notes and your tasks. Connected to Claude, all of that becomes something you can question in plain words: no reopening the app, no pasting a transcript to find out who said what.
Track down a decision. search_meetings spots the right meeting and get_meeting opens it, so Claude reads the transcript and answers. Search covers titles, summaries and notes, not the transcripts themselves.
Get ready for the next one. list_upcoming_meetings and get_upcoming_meeting look ahead, with any available pre-reads, and resolve_calendar_link ties an invite or video link back to its calendar event.
Keep follow-ups moving. search_tasks finds tasks, while add_task and update_task add or adjust them according to the directory sheet. Wispr Flow's help article still calls access read-only; the limits section puts both texts side by side.
What Claude does not do, per Wispr Flow: alter or erase a meeting or note, or read dictation history or Notetaker chat history. And nothing runs on its own: no tool wakes up when a meeting ends. That is a job for an automation tool, a different trade; the Integrations hub covers it, and the Claude connectors hub lists the others.
The vocabulary in one minute
Five words you will meet while connecting Wispr Flow.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant talk to an outside service. You will meet the acronym elsewhere.
Connect Wispr Flow to Claude in three steps
- 01
Find Wispr Flow in Claude
In Claude's settings, open Customize, then Connectors, and locate Wispr Flow. On a Team or Enterprise workspace, an Owner or Primary Owner first has to enable the connector for the organization.
- 02
Start the connection
Click Connect on its row, then sign in to Wispr Flow in the window the service opens itself. If the link ever breaks, use Disconnect and connect again from the same row.
- 03
Approve, then switch it on per chat
Read the authorization screen first: it sets what the access covers. Wispr Flow then says to turn the connector on for the conversation, through the + button in the chat box, then Connectors.
The 16 tools, grouped by what they do
Wispr Flow gives Claude 16 tools: 14 that read your account, 2 that change something in it.
Fourteen lookup tools and two that handle your tasks, according to the directory sheet. Names stay exactly as Claude shows them.
- 14 read
- 2 write
What Claude reads (14)
14 toolsMeetings, calendar, Scratchpad notes, tasks and account identity, all as lookups.
get_account_info
Account identity is one of the things Wispr Flow lists as readable through the connector; no source describes this tool beyond that.
get_calendar_event
Wispr Flow lists calendar events and their linked recordings among what the connector can read. No source describes this tool on its own, beyond that general line.
get_meeting
Opens a recorded meeting so Claude can read it and answer your question: summary, notes, transcript, attendees. Long transcripts arrive in portions, summaries in full.
get_meeting_by_calendar_id
Falls under the access to calendar events and their linked recordings, as Wispr Flow describes it. No source details this tool any further than that line.
get_scratchpad_note
Opens one of your Scratchpad notes. The directory sheet presents referencing those notes alongside your meeting history as one of the connector's uses.
get_task
Tasks are on the list of what Wispr Flow says the connector can read, and the directory sheet talks about tracking action items. No source describes this particular tool.
get_upcoming_meeting
Looks up one upcoming meeting, with its pre-reads when they exist. The directory sheet frames this as a way to prep before you walk in.
list_meeting_series
Covers recurring meetings, which Wispr Flow lists as readable. Ask what was discussed last time about a meeting that does not repeat, and the answer says it is not recurring.
list_upcoming_meetings
Lists the meetings ahead of you that Wispr Flow knows about, with pre-reads where they are available, in line with the sheet's promise to keep you on top of your calendar.
resolve_calendar_link
Ties a calendar or conference link back to the event it belongs to. Wispr Flow names this capability explicitly in its help article.
search_calendar_events
Wispr Flow groups calendar events with their linked recordings in what the connector can read. No source describes this search tool on its own.
search_meetings
Spots the meetings that match your question. Search covers titles, summaries and notes, not the text of transcripts.
search_scratchpad_notes
Digs through your Scratchpad notes so you can reference them next to your meeting history, as the directory sheet from the publisher describes.
search_tasks
Searches the action items Wispr Flow keeps, which the directory sheet presents as the way follow-ups do not slip. Wispr Flow's help article also lists tasks among what the connector can read.
What Claude adds or adjusts (2)
2 toolsTwo task tools, advertised by the directory sheet and contradicted by the publisher's help article. No source describes a confirmation of their own: the general rule below applies.
add_task
Approval: see the ruleAdds a task to your Wispr Flow account, according to the directory sheet, which advertises creating action items so follow-ups do not slip.
update_task
Approval: see the ruleUpdates an existing task, per the directory sheet, which advertises updating action items alongside creating and searching them.
What Claude asks before it acts
By default, Claude stops and asks before every action it takes on an account on your behalf. No source describes a confirmation specific to add_task or update_task: that default is what covers them.
On Team and Enterprise, workspace owners decide whether a member may let some actions through without approval, and they can cap what a connector does for the whole organization. On the Wispr Flow side, authorization is account-wide and includes existing content, with no per-meeting consent. To cut access, remove Wispr Flow from Claude's connectors: the app itself has no disconnect control, so the cut always happens on Claude's side.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that information is not published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables them for the organization first. On the Wispr Flow side, your account needs Notetaker and MCP access. For the connector's current status, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing fires on its own when a meeting ends.
Only the publisher documents this connector; Anthropic has no page about it, and the publisher's two texts disagree on tasks. The tool list remains an observed floor, not a guarantee, and the directory badge is not a security audit. Anthropic writes on every sheet that it does not choose the tools a publisher exposes and cannot promise they behave as described. Only connect what comes from a publisher you know, here Wispr Flow itself.
Can the Wispr Flow connector write tasks?
- Claude directory sheet (publisher description and tool list) ↗October 1, 2026The sheet lists add_task and update_task and advertises creating, updating and searching action items.
- Wispr Flow help article ↗September 30, 2026The article calls access read-only: no creating, editing or deleting meetings or notes, and no reading dictation history.
What this page followsNeither is out of date, and neither settles the question for tasks: the article explicitly rules out meetings and notes, not tasks. The sheet's tool list is what Claude sees, so this page follows it for grouping, but check on your own account before relying on an add or an update.
Need help connecting Wispr Flow to Claude?
A person reads every message.