Skip to main content
Book a demo

Connect Miro to Hermes

Give Hermes governed access to Miro’s 64 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Hermes setup guide

Set up

Add Miro to Hermes in four steps

Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.

  1. 1

    Approve Miro in Runlayer

    Add Miro from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Hermes to Runlayer

    Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Miro’s 64 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Hermes setup guide
  3. 3

    Sign in to Miro

    Sign in the way Miro requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Miro from Hermes

    Miro’s approved tools appear in Hermes. Every call is checked against policy and recorded.

Tools

64 Miro tools in Hermes

Runlayer policy decides which of these Hermes users can call.

  • Create blog post

    Create a new blog post in a Miro space overview.

  • List blog post

    List all blog posts or updates or feed in a Miro space overview.

  • Update blog post

    Update an existing blog post in a Miro space overview.

  • Create board

    Create a new Miro board.

  • Board create format

    Create a typed board format, such as a table, timeline, kanban, document, diagram, prototyping container, slide container, activities board, or embed.

  • Board get space

    Find which space a board belongs to.

  • Board list items

    DEPRECATED: superseded by canvas_search and canvas_read_as_svg, removed on September 14, 2026.

  • Board move

    Move an existing Miro board under a space or folder.

See all 64 Miro tools

Control

What Runlayer can see and stop in Hermes

Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.

  • Gateway policy (available)

    Every Miro call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Hermes runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output in Hermes and show a message in its place.

  • Redact output in place (not available)

    Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Hermes

  • Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.

Frequently asked questions

Connect more

Find another combination