Skip to content
MCP logoHedy logo

Connect MCP to Hedy

Move data between MCP and Hedy the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

MCP triggers
1
MCP actions
1
Hedy triggers
5
Hedy actions
19

Automation ideas

What you can build with MCP and Hedy

A few flows teams run between MCP and Hedy. Use one as a starting point, or build your own from scratch.

  • MCP Tool in MCP creates Get Session in Hedy

    Creates a tool that MCP clients can call to execute this flow

  • Session Created in Hedy creates Reply to MCP Client in MCP

    Triggers when a new session is created in Hedy.

  • MCP Tool in MCP creates List Sessions in Hedy

    Creates a tool that MCP clients can call to execute this flow

  • Session Ended in Hedy creates Reply to MCP Client in MCP

    Triggers when a session is completed in Hedy.

  • MCP Tool in MCP creates Get Highlight in Hedy

    Creates a tool that MCP clients can call to execute this flow

  • Session Exported in Hedy creates Reply to MCP Client in MCP

    Triggers when a user manually exports a session via the app. Payload includes exportedAt instead of endTime.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in MCP and acts in Hedy, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.