Miro
Create and read Miro boards, sticky notes, cards, shapes, connectors and tags.
About
Miro ships in the w6w first-party pack. It declares 27 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.miro- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Project Management
Overview
Miro brings visual collaboration boards into a workflow — creating and reading boards, and populating them with sticky notes, cards, shapes, text, frames, images and connectors. Board actions list, read, create, copy, update and delete boards, with board-copy built for the common case of duplicating a template board to start a new one.
Item actions cover the full canvas: list a board’s items overall, scoped to one frame, or filtered by tag, and create, move or delete any item type — including a bulk-create action for adding up to twenty mixed items in a single call. Tags can be created, listed and attached to items for organizing a busy board, and connectors draw lines between two items to show relationships. Sharing actions list who already has access to a board and invite new people by email.
The app stays on Miro’s stable API surface rather than the experimental endpoints Miro reserves the right to change without notice.
Build with Miro
Three routes to the same 27 actions. The Workflow tab is generated from Miro's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Miro's real ids.
{
"manifestVersion": "2",
"name": "miro-example",
"steps": [
{
"id": "board-copy",
"uses": {
"app": "io.w6w.miro",
"action": "board-copy",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"copyFrom": "<copyFrom>"
}
}
]
}Here are some of the things you can do
-
Copy a board
performboard-copy -
Create a board
performboard-create -
Get a board
readboard-get -
List boards
readboard-list -
List board members
readboard-member-list
+22 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Miro, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Miro. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "board-copy",
payload: {
copyFrom: "<value>",
// name: "<value>",
// description: "<value>",
// teamId: "<value>",
// policy: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action board-copy --payload '{"copyFrom":"<value>"}'Give an AI agent Miro — without giving it Miro's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.miro#board-copy",
"input": {
"copyFrom": "<copyFrom>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Miro connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Miro's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Miro itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Miro declares its own checks, so its health is a property of the app rather than something the host guesses at.
Miro platform status
Statuspage rollup for status.miro.com. Unauthenticated and unsigned. Miro publishes no per-component breakdown, so only the rollup is reported.