Skip to main content
Book a demo

Connect Miro to Gemini CLI

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

Book a demo Gemini CLI setup guide

Set up

Add Miro to Gemini CLI in four steps

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

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

    Gemini CLI 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 Gemini CLI

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

Tools

64 Miro tools in Gemini CLI

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Gemini CLI 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 Gemini CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Gemini CLI’s model sees it.

  • Redact output in place (not available)

    Gemini CLI can only add text to a tool result, not replace it, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

In Gemini CLI

  • Enforcement needs Gemini CLI 0.26.0 or newer.
  • When Runlayer blocks a call or its output, Gemini CLI shows the model the block reason instead.

Frequently asked questions

Connect more

Find another combination