How to integrate Wispr Flow MCP with Hermes

Connect Hermes 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.

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

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Wispr Flow account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Wispr Flow MCP with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,500+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Wispr Flow with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Wispr Flow

Ask your agent to connect to Wispr Flow, or simply request any Wispr Flow-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Wispr Flow connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Wispr Flow or request any Wispr Flow-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Wispr Flow MCP server, 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.

Way Forward

With Wispr Flow connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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).

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. Hermes 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