SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Wispr Flow MCP to Claude

Connect Claude Web, Desktop and Cowork to Wispr Flow MCP. Summarize today's product sync meeting transcript, list participants and roles from last meeting, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Wispr Flow MCP logoWispr Flow MCP
Dcr Oauth

Wispr Flow MCP is a meeting intelligence service that captures notes, transcripts, participants, and meeting artifacts. Give authorized agents read-only access within existing Wispr Flow permissions.

14 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Wispr Flow account to Claude via Composio Connect, enabling it to summarize today's product sync meeting transcript, list participants and roles from last meeting, fetch pre-read files for tomorrow's demo, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Wispr Flow MCP with

ChatGPTHermesAtomic Agent

Connecting Wispr Flow to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Wispr Flow account

Back in Claude, ask it to connect to Wispr Flow or give it any Wispr Flow-related task.

For example, ask Claude to:

  • "Summarize today's product sync meeting transcript"
  • "List participants and roles from last meeting"
  • "Fetch pre-read files for tomorrow's demo"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Wispr Flow account is ready to use.

What is the Wispr Flow Claude Connector, and what's possible with it?

The Wispr Flow MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Wispr Flow account. It provides structured and secure access so your agent can perform Wispr Flow operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Wispr Flow?

The connector can show as connected, but Claude must use it in each Wispr Flow conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Wispr Flow again.

2. Why does Claude show an MCP server error before Wispr Flow connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Wispr Flow.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Wispr Flow.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Wispr Flow authorization link not work?

The Composio connector is one server. Your Wispr Flow account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Wispr Flow connection.
  • Composio creates a fresh Wispr Flow authorization link.
  • Open that link in your browser and finish the Wispr Flow sign-in.

4. Why do Wispr Flow actions fail after they worked before?

The Wispr Flow connection can expire or lose permission.

  • Ask Claude to inspect the Wispr Flow connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Wispr Flow account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Wispr Flow.
  • If the action still fails with a permission error, check that the connected account has that permission in Wispr Flow itself.

5. How do I switch to a different Wispr Flow account?

Claude can manage the Wispr Flow connection for you.

  • Ask Claude to disconnect or delete the current Wispr Flow account.
  • Ask Claude to connect Wispr Flow again.
  • Open the new Composio authorization link for Wispr Flow.
  • Sign in with the other Wispr Flow account in the browser.
  • After the account connects, ask Claude to retry the Wispr Flow task.

6. Why is my Wispr Flow connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Wispr Flow connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Wispr Flow tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Wispr Flow.
TOOLS

Supported Tools

Every Wispr Flow MCP action and event your agent gets out of the box.

Get account info

Get the authenticated user's own identity — their name and any display-name aliases they appear under on their calendar.

Get calendar event

Get a single calendar event by its calendar_id (the id returned by search_calendar_events or resolve_calendar_link).

Get meeting

Get a bounded range of the markdown notes, the complete derived markdown summary, the complete attendee list without email addresses, and (when requested and available) a bounded range of the recorded transcript of a specific meeting.

Get meeting by calendar

Get the recorded meeting — a bounded range of its markdown notes, the complete derived markdown summary, and (when requested and available) a bounded transcript range — captured for a calendar event, by its calendar_id (from search_calendar_events or resolve_calendar_link).

Get meeting participants enriched

Who was in a meeting and which one of them is the user.

Get scratchpad note

Get a bounded range of a specific note's normalized text.

Get upcoming meeting

Get a single upcoming calendar event by calendar_id, with its latest pre-read when one is available.

List meeting series

Given a meeting_id (from search_meetings) for a recurring meeting, list every recorded occurrence of that recurring series — newest first, including the meeting you passed in.

List upcoming meetings

List the user's upcoming calendar events in the next window_hours (default 24, max 168), soonest first, with an attendee preview (up to 5 structured attendees plus attendee_count) and each event's latest pre-read attached when one has been generated.

Resolve calendar link

Resolve a calendar/meeting URL the user pasted (a Google Calendar event link, or a Meet/Zoom conference link) to the matching calendar event — title, time, attendees, conference URL, and its calendar_id.

Resolve share link

Resolve a Wispr Flow shared-notes link the user pasted (https://notes.

Search calendar events

Search or list the user's Google Calendar events.

Search meetings

Search or list the user's meetings captured by Wispr Flow Meeting Recorder.

Search scratchpad notes

Search or list the user's notes (Wispr Flow scratchpad).

FRAMEWORKS

How to build Wispr Flow MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Wispr Flow MCP with ChatGPT

Hermes logo

Hermes

Use Wispr Flow MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Wispr Flow MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone Wispr Flow MCP server, the agents and LLMs can only access a fixed set of Wispr Flow tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Wispr Flow and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Wispr Flow tools.

Yes, absolutely. You can configure which Wispr Flow scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Wispr Flow data and credentials are handled as safely as possible.

Start with Wispr Flow MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Wispr Flow MCP tool your agent needs.Free to start.

Start building