Connect Miro to Codex
Give Codex governed access to Miro’s 64 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Miro to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Miro in Runlayer
Add Miro from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Miro’s 64 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 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
Use Miro from Codex
Miro’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
64 Miro tools in Codex
Runlayer policy decides which of these Codex 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.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Miro call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more