Skip to main content

Connect Miro to OpenCode

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

Set up

Add Miro to OpenCode in four steps

Admins approve the server once. Everyone in OpenCode 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 OpenCode to Runlayer

    Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Miro’s 64 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    OpenCode 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 OpenCode

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

Tools

64 Miro tools in OpenCode

Runlayer policy decides which of these OpenCode 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 OpenCode

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination