otheroauth2

Wispr Flow MCP

Wispr Flow MCP gives authorized agents read-only access to meeting notes, summaries, transcripts, participants, scratchpad notes, calendar events, recurring meetings, and upcoming-meeting pre-reads within the user's existing Wispr Flow permissions.

Verdict

Wispr Flow MCP connects your team's recorded meetings and calendar to Switchy. @mention it to pull transcripts, summaries, and notes from past calls, check who attended a meeting, or preview what's on someone's schedule. It reads your calendar events and retrieves the markdown notes Wispr Flow captured during recordings. Useful for teams that record standups, client calls, or sprint reviews and want AI to reference what was said without rewatching video. Requires OAuth to your Wispr Flow account; the MCP sees only meetings you have access to.

Common use cases

  • Pull action items from yesterday's standup
  • Summarize what a client said in last week's call
  • Check who attended a recurring sprint review
  • Preview pre-read notes for an upcoming meeting
  • Search meeting transcripts for a specific decision

Integration

Vendor
Wispr Flow MCP
Category
other
Auth
OAUTH2
Tools
14
Composio slug
wispr_flow_mcp

Tools

  • Get account info

    Get the authenticated user's own identity — their name and any display-name aliases they appear under on their calendar. Call this first for first-person questions ('what did I commit to', 'my meetings', 'who did I meet with', 'did I owe hi

  • Get calendar event

    Get a single calendar event by its calendar_id (the id returned by search_calendar_events or resolve_calendar_link). Returns title, time, attendees, description, and conference URL. Every timestamp in the response is UTC (ISO 8601, ending i

  • 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. Use a

  • 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

  • Get meeting participants enriched

    Who was in a meeting and which one of them is the user. Returns the user's own name/email/domain plus every participant (speaker-map people and calendar attendees) with name, contact_id, emails, whether they spoke, organizer, and relationsh

  • Get scratchpad note

    Get a bounded range of a specific note's normalized text. The first range is returned by default. Call after search_scratchpad_notes when the user wants the note's content; when truncated, repeat with view_content.start_char set to the exac

  • Get upcoming meeting

    Get a single upcoming calendar event by calendar_id, with its latest pre-read when one is available. Refuses past events — use get_meeting_by_calendar_id for the recorded notes of a past event, or get_calendar_event for generic event metada

  • 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. Use to answer 'what did we discuss last time this met', 'what's

  • 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

  • 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. Use this whenever the user pastes su

  • Resolve share link

    Resolve a Wispr Flow shared-notes link the user pasted (https://notes.wisprflow.ai/shared/…) to the shared meeting note: its title, Flow Summary (whose next-steps section holds the meeting's action items), owner, and the caller's role. Use

  • Search calendar events

    Search or list the user's Google Calendar events. Use to find meetings by who's on them (attendee_emails — the precise way to answer 'meetings with alex@acme.com', or 'with both alex and bob' via attendee_match=all), by keyword in the title

  • Search meetings

    Search or list the user's meetings captured by Wispr Flow Meeting Recorder. Use when the user asks about their meetings, calls, standups, 1:1s, syncs, or anything discussed in a recorded conversation. Returns the most recently modified meet

  • Search scratchpad notes

    Search or list the user's notes (Wispr Flow scratchpad). Use whenever the user asks about their notes, scratchpad, jottings, or anything they've written down. Returns the most recently modified notes when no query is given; case-insensitive

Setup

Setup guide

  1. 11. Open your Switchy workspace and navigate to Integrations in the left sidebar. 2. Find Wispr Flow MCP in the catalog and click Connect. 3. You'll be redirected to Wispr Flow's OAuth consent screen; sign in with the account that has access to your recorded meetings. 4. Grant the requested scopes — read access to your calendar events, meeting transcripts, and notes. 5. Switchy confirms the connection and shows Wispr Flow MCP as active. 6. Open any Project and type '@Wispr Flow MCP get my upcoming meetings' to test; the MCP should return your next scheduled events. 7. To retrieve a past meeting's notes, first search by topic or date, then ask for the full transcript or summary using the meeting ID returned.

What teammates see: by default, memories from Wispr Flow MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Standup Action Items

@Wispr Flow MCP search my meetings from the past two days with 'standup' in the title, then pull the notes and list every action item or commitment someone made.

Client Call Summary

@Wispr Flow MCP find the meeting with 'Acme Corp' in the title from last Thursday, then give me a two-paragraph summary of what we discussed and any decisions we reached.

Meeting Attendee Lookup

@Wispr Flow MCP get the participant list for the meeting titled 'Q1 Planning' on January 15, and tell me which attendees are from our domain versus external guests.

Pre-Read for Upcoming Call

@Wispr Flow MCP show me the pre-read notes for my next meeting with 'Product Sync' in the title, so I know what to prepare.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Wispr Flow MCP find my scratchpad note about the API redesign and pull out the open questions

Output

Your scratchpad note 'API v3 Redesign Brainstorm' (last edited 3 days ago) contains four open questions: (1) Should we version at the endpoint level or globally? (2) How do we handle backward compatibility for mobile clients still on v2? (3) Do we need rate-limit tiers for enterprise vs. free accounts? (4) What's the migration timeline if we deprecate v2 endpoints? The note also includes a rough schema draft and links to two Slack threads.

Notes

This showcases Wispr Flow's scratchpad search and retrieval. The MCP calls search_scratchpad_notes by keyword, then get_scratchpad_note to fetch content. The AI synthesizes the 'open questions' from unstructured markdown. If the note is long, the response may be truncated—prompt again with a range offset to retrieve more. No side-effects; read-only.

Prompt

@Wispr Flow MCP who attended the last three sprint retros and what were the recurring themes?

Output

The last three 'Sprint Retro' meetings (Oct 15, Oct 1, Sep 17) included you, Emma (PM), Jordan (eng lead), and 4–6 rotating engineers. Recurring themes across all three: (1) deployment pipeline delays causing late-week crunches, (2) unclear acceptance criteria leading to rework, and (3) requests for more dedicated pairing time. The Oct 15 retro specifically noted improvement in story estimation accuracy after adopting planning poker.

Notes

This example pairs multiple MCP tools—list_meeting_series to find recurring meetings, get_meeting to retrieve notes and attendees for each occurrence, then AI reasoning to identify patterns. Demonstrates cross-meeting synthesis. Requires that retros were recorded and that the user has access. Response quality depends on how structured the original meeting notes were.

Use-case deep-dives

Async standup for remote teams

When recorded meetings replace live standups at 8-person scale

A distributed 8-person engineering team runs standups across three time zones. Half the team can't make the live slot. Wispr Flow records the standup, transcribes it, and surfaces a markdown summary with action items. The PM searches 'what did Sarah commit to this week' and pulls the answer from three standup transcripts without watching video. This works when your standups are short (under 20 minutes), structured, and happen at least twice a week. If your team is larger than 12 or your standups are unstructured rambles, the transcript search gets noisy and you're better off with a shared doc. The OAuth2 flow means each person authenticates once and Switchy can pull their own meeting history on demand.

Client call prep for account teams

Pre-reads and participant lookup before high-stakes calls

A 3-person account team has a renewal call with a customer they haven't spoken to in six weeks. The AE opens Switchy, searches 'last meeting with Acme Corp', and pulls the markdown summary plus attendee list. Wispr Flow's get_upcoming_meeting tool surfaces the pre-read for today's call and enriches participant data so the team knows who's joining and whether they've met before. This scenario wins when you have under 30 customer accounts and your calls are recorded in a calendar system Wispr Flow syncs with. If you're managing 100+ accounts or your CRM is the source of truth, you need a different integration. The 14-tool scope gives you calendar, transcript, and participant lookup in one MCP.

Sprint retro note consolidation

When scratchpad search beats manual note-taking for retrospectives

A 5-person product squad runs biweekly retros. Each person jots notes in Wispr Flow's scratchpad during the sprint — bugs they hit, process friction, wins. At retro time, the facilitator searches 'scratchpad notes last two weeks' and pulls every team member's jottings into a single Switchy thread. The get_scratchpad_note tool returns normalized text so the facilitator can theme the notes without opening six tabs. This works when your team already uses Wispr Flow for meeting notes and your retros are under 60 minutes. If your team doesn't have a shared note-taking habit or your retros are quarterly, the scratchpad stays empty and you're better off with a dedicated retro tool.

Frequently asked

What does the Wispr Flow MCP do in Switchy?

It connects your Wispr Flow meeting recordings and notes to Switchy's AI workspace. Your team can search past meeting transcripts, pull calendar event details, retrieve pre-reads for upcoming meetings, and access scratchpad notes — all without leaving Switchy. The MCP exposes 14 tools covering calendar lookups, meeting summaries, participant lists, and note retrieval.

Do I need admin access to connect Wispr Flow via OAuth?

No. Wispr Flow uses OAuth2, so any team member with a Wispr Flow account can authorize Switchy to read their own meetings, calendar events, and notes. You're granting access to your personal data — not org-wide recordings. If your team shares a Wispr Flow workspace, each person connects their own account separately.

Can the Wispr Flow MCP edit or delete my meeting notes?

No. The MCP is read-only. It retrieves meeting transcripts, summaries, calendar events, and scratchpad notes but cannot modify or delete anything in Wispr Flow. If you need to edit a note or remove a recording, you still do that in the Wispr Flow app directly.

Why use this MCP instead of opening Wispr Flow in a browser?

Speed and context. Switchy's AI can search across multiple meetings, cross-reference calendar attendees with other data sources, and pull exact transcript snippets into a shared workspace — all in one query. You skip the manual hunt through Wispr Flow's UI and get structured answers your whole team can reference.

Who on the team should connect the Wispr Flow MCP?

Anyone who records meetings in Wispr Flow and wants Switchy to search their notes. Each connection is scoped to one person's account, so if three teammates use Wispr Flow, all three should connect it separately. That way Switchy can pull from everyone's recordings when answering team questions.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.