Connect Miro to Windsurf
Give Windsurf governed access to Miro’s 64 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Miro to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf 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 Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Miro’s 64 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf 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 Windsurf
Miro’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
64 Miro tools in Windsurf
Runlayer policy decides which of these Windsurf 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 Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Miro call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf 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 Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more