Miro

Live

OAUTH 2.0

VISUAL COLLABORATION

Every board, sticky note, and collaborative diagram your team creates lives in Miro. Miro MCP gives your agent authenticated access to visual workspaces scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Miro account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Miro
agent · Acme Q3
Run
Find all retro boards from this sprint and summarize the action items added as stickies.
S
miro_boards_list
78ms
Visual collaboration agent
3 retro boards from this sprint. Sprint 42 Retro: 12 stickies, 5 action items (improve deploy process, fix auth tests, add monitoring). Sprint 41: 9 stickies, 3 action items. Planning board: 14 stickies.
Sources: 3 retro boards, this sprint
miromcp
3 boards
18:29
Message Claude...

Tools your visual collaboration agent reaches for on Miro, scoped per user.

CALL ANY TOOL
List boards and items, create sticky notes, and search across the visual workspace.
miro_boards_list
List boards
List Miro boards accessible to the user with project filter.
Parameters
Name
Type
Required
Description
project_id
string
Optional
Project ID filter
limit
integer
Optional
Max boards
miro_board_get
Get board
miro_items_list
List items
miro_sticky_create
Create sticky note
miro_boards_search
Search boards
Build your Agent
Drop the toolkit in, point it at the user, and your visual collaboration agent can use Miro from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["miro"], toolNames: ["miro_boards_list", "miro_board_get", "miro_items_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["miro"], toolNames: ["miro_boards_list", "miro_board_get", "miro_items_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["miro"], toolNames: ["miro_boards_list", "miro_board_get", "miro_items_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/miro",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Miro.
Boards & items
Copy the prompt
Copied
List all boards in [project].
Copy the prompt
Copied
Get items on [board name].
Copy the prompt
Copied
Find boards with [keyword] in title.
Copy the prompt
Copied
List all sticky notes on [board].
Action & creation
Copy the prompt
Copied
Create a sticky note on [board]: [text].
Copy the prompt
Copied
Search boards for [keyword].
Copy the prompt
Copied
Get metadata for [board name].
Copy the prompt
Copied
List all frames on [board].
Reporting
Copy the prompt
Copied
Which boards were updated this sprint?
Copy the prompt
Copied
List boards shared with the whole team.
Copy the prompt
Copied
How many items are on [board]?
Copy the prompt
Copied
Find boards with no activity in 14 days.
SEE HOW AUTH WORKS
Users authorize Miro once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Miro
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Miro
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Miro
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Miro
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other visual collaboration agents and MCP connectors. Working code, live demos, fork what fits.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Miro today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Miro as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Miro oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Miro?
Yes. Pass a tool name filter to listScopedTools so the visual collaboration agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Miro.
What happens when a user revokes Miro access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent access boards in teams the user is not a member of?
No. Board access inherits the authorizing user's Miro OAuth scope. Boards in teams or projects the user hasn't joined are not returned. Private boards follow Miro's native access model.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""miro"": {
""url"": ""https://mcp.scalekit.com/miro"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.miro]
url = ""https://mcp.scalekit.com/miro""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""miro"": {
""url"": ""https://mcp.scalekit.com/miro"",
""type"": ""http""
}
}
}