Skip to main content

Wispr Flow MCP integration

AI utilities connector, available on Zeplik

Wispr Flow MCP is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Wispr Flow MCP and Zeplik can act on your AI for you: Wispr Flow MCP gives authorized agents read-only access to meeting notes, summaries, transcripts, participants, scratchpad notes, calendar events,. You stay in the conversation while the assistant does the work in Wispr Flow MCP directly.

Zeplik exposes 12 read actions and 2 write actions for Wispr Flow MCP. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Wispr Flow MCP without your consent.

Try Wispr Flow MCP on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Wispr Flow MCP

Read from Wispr Flow MCP (12)

Runs automatically in any conversation.

  • 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 him') so you know which person the user is among a meeting's attendees.

  • 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 in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 after search_meetings to answer anything about what was discussed, decided, the action items, or who-said-what. Returns start/end times for when the meeting happened. The raw Lexical notes JSON is intentionally omitted; use `content` for the paginated markdown note body and `summary` for the Flow Summary body, whose next-steps section holds the meeting's action items. Prefer view_transcript={} and synthesize your answer from the transcript itself: the notes are an auto-generated summary that can drop details, while the transcript is the verbatim source of truth. Omit view_transcript only when you've judged the notes alone are enough (e.g. a quick high-level recap). Transcript responses are character-bounded; when truncated, use the continuation offset in the marker to request the next range. Content is also character-bounded and returns its first range by default; use view_content with the continuation offset to read more. The summary is always returned in full. share_link is the meeting's notes page in Wispr Flow. Give it to the user whenever they ask for a link. Who else can open it depends on that meeting's sharing setting, and this server cannot read or change that setting. If the user wants to change who a link works for, tell them to open the Wispr Flow app, go to the Notetaker tab, click the menu to the right of the meeting, and click Share — that opens the sharing settings for that meeting. A meeting with no share_link has no notes page yet — say so rather than guessing a URL. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • Get meeting by calendar id

    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). Use this to answer 'what was discussed / decided / the action items' for a meeting on the user's calendar. Returns start/end times for when the meeting happened. The raw Lexical notes JSON is intentionally omitted; use paginated `content` and complete `summary`, whose next-steps section holds the meeting's action items. Prefer view_transcript={} and synthesize from the transcript itself: the notes are an auto-generated summary that can drop or distort details, while the transcript is the verbatim source of truth. Omit view_transcript only when you've judged the notes alone are enough. When truncated, use the continuation offset in the marker to request the next range. Content returns its first bounded range by default; use view_content with its continuation offset to read more. Errors if no recording is linked to that event. share_link is the meeting's notes page in Wispr Flow. Give it to the user whenever they ask for a link. Who else can open it depends on that meeting's sharing setting, and this server cannot read or change that setting. If the user wants to change who a link works for, tell them to open the Wispr Flow app, go to the Notetaker tab, click the menu to the right of the meeting, and click Share — that opens the sharing settings for that meeting. A meeting with no share_link has no notes page yet — say so rather than guessing a URL. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 relationship to the user (self | colleague | external | unknown, by email domain). Omits the caller, mention-origin people, and Google room/equipment attendees. Calendar RSVP is not included. When listed, get_participant_contacts takes contact_ids from this result for LinkedIn, job title, and company.

  • 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 exact continuation offset in the marker.

  • 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 metadata. Pass include_preread=false to skip the pre-read fetch. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 recurred across these syncs', or to catch up before today's instance. Errors if the meeting isn't linked to a recurring calendar series. Each occurrence has the same shape as a search_meetings result (call get_meeting for full notes/transcript). Results are paginated, newest first. If the response's has_more is true there are more matches: call again with cursor set to the returned next_cursor (copied verbatim) to continue. When more remain, a 'more' field spells out how many and how to continue. To answer 'all'/'every'/'ever' questions, keep paging until has_more is false. Paging is capped at 1000 results per query; truncated=true means more matches exist beyond the cap — narrow the query. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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. Use to answer 'what meetings are coming up' or 'prep me for my next meeting'. For today or another whole local day, use search_calendar_events with since/until. Events without a generated pre-read return preread: null — pre-reads are produced on-demand by the desktop app, not by this tool. Results are paginated, newest first. If the response's has_more is true there are more matches: call again with cursor set to the returned next_cursor (copied verbatim) to continue. When more remain, a 'more' field spells out how many and how to continue. To answer 'all'/'every'/'ever' questions, keep paging until has_more is false. Paging is capped at 1000 results per query; truncated=true means more matches exist beyond the cap — narrow the query. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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/description, or within a date window. For a whole local calendar day (including earlier events), use since and until. Returns each event's title, time, conference URL, and an attendee preview (up to 5 structured attendees plus attendee_count). Use get_calendar_event for the complete attendee list. Note: these are calendar events, not the recorded meeting notes. Results are paginated, newest first. If the response's has_more is true there are more matches: call again with cursor set to the returned next_cursor (copied verbatim) to continue. When more remain, a 'more' field spells out how many and how to continue. To answer 'all'/'every'/'ever' questions, keep paging until has_more is false. Paging is capped at 1000 results per query; truncated=true means more matches exist beyond the cap — narrow the query. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 meetings when no query is given. For meetings on a particular day, pass since/until (when the meeting happened, half-open). Filter by who was there with attendee_emails (matched against the meeting's linked calendar event) — the precise way to answer 'my meetings with alex@acme.com'. Each result lists up to 5 attendees (more are summarized — call get_meeting for the full list), start/end times, and a has_transcript flag; when true, follow up with get_meeting and view_transcript={} and answer from the transcript rather than the lossy notes summary. share_link is the meeting's notes page in Wispr Flow. Give it to the user whenever they ask for a link. Who else can open it depends on that meeting's sharing setting, and this server cannot read or change that setting. If the user wants to change who a link works for, tell them to open the Wispr Flow app, go to the Notetaker tab, click the menu to the right of the meeting, and click Share — that opens the sharing settings for that meeting. A meeting with no share_link has no notes page yet — say so rather than guessing a URL. Results are paginated, newest first. If the response's has_more is true there are more matches: call again with cursor set to the returned next_cursor (copied verbatim) to continue. When more remain, a 'more' field spells out how many and how to continue. To answer 'all'/'every'/'ever' questions, keep paging until has_more is false. Paging is capped at 1000 results per query; truncated=true means more matches exist beyond the cap — narrow the query. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 substring match otherwise. Results are paginated, newest first. If the response's has_more is true there are more matches: call again with cursor set to the returned next_cursor (copied verbatim) to continue. When more remain, a 'more' field spells out how many and how to continue. To answer 'all'/'every'/'ever' questions, keep paging until has_more is false. Paging is capped at 1000 results per query; truncated=true means more matches exist beyond the cap — narrow the query.

Act in Wispr Flow MCP (2)

Runs only after you enable write access.

  • 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 such a link instead of guessing at its contents. To then pull the event again later, use get_calendar_event with the returned calendar_id. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

  • 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 this whenever the user pastes such a link instead of guessing at its contents — shared notes are usually other people's meetings, which search_meetings/get_meeting (the user's own meetings) will never find. The owner also receives their user-authored My Notes. Set view_transcript={} when the user needs source-level detail: a bounded transcript range is returned only when the caller owns the note or is an explicitly invited recipient AND the owner's organization shares transcripts. Domain/team access, anyone-with-link access, or a notes-only organization returns transcript=null plus a transcript_access explanation when requested. When truncated, use the continuation offset in the marker to request the next range. Errors if the link is not a share link or no shared note is accessible for it. Every timestamp in the response is UTC (ISO 8601, ending in 'Z'). Convert times to the user's local time zone before presenting them — do not show the raw UTC time to the user.

How to connect Wispr Flow MCP

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Wispr Flow MCP immediately.

  2. Connect Wispr Flow MCP

    Open Settings and go to Connectors, then press Connect on Wispr Flow MCP. You can also connect from the Wispr Flow MCP page in the app.

  3. Approve access to Wispr Flow MCP

    Approve access on Wispr Flow MCP's secure consent screen. You are returned to Zeplik and can start giving instructions that use Wispr Flow MCP.

Frequently asked questions

Can I use Wispr Flow MCP with Zeplik?
Yes. Wispr Flow MCP is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Wispr Flow MCP account inside any conversation.
What can Zeplik do with Wispr Flow MCP?
Once connected, Zeplik has 12 read and 2 write actions for Wispr Flow MCP. Wispr Flow MCP gives authorized agents read-only access to meeting notes, summaries, transcripts, participants, scratchpad notes, calendar events,.
How do I connect Wispr Flow MCP to Zeplik?
You connect Wispr Flow MCP with a secure one-click sign-in (OAuth): press Connect in Settings under Connectors and approve access on Wispr Flow MCP's consent screen.
Does Zeplik change things in Wispr Flow MCP without asking?
No. Zeplik reads from Wispr Flow MCP by default. Any action that changes data in Wispr Flow MCP requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Wispr Flow MCP cost?
Connecting Wispr Flow MCP is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related ai utilities integrations

More on Zeplik

Connect Wispr Flow MCP to your AI assistant

Every model, one chat. Bring Wispr Flow MCP into Zeplik and let the assistant do the work.