2,500+ MCP servers ready to use
Vinkius

Miro MCP Server for Claude Desktop 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Miro and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "miro": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Miro
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Miro MCP Server

Connect your Miro account to any AI agent and take full control of your visual collaboration through natural conversation.

Claude Desktop is the definitive way to connect Miro to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 14 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Board Management — List, create, update and inspect boards with their descriptions, owners and permissions
  • Item Operations — Browse all widgets on a board (sticky notes, cards, shapes, texts, connectors, images) with their content and positions
  • Content Creation — Create sticky notes and cards programmatically with custom content and canvas positions
  • Member Management — List board members and add new users with specific roles (owner, admin, editor, commenter, viewer)
  • Comments — Read and add comments on boards for async collaboration feedback

The Miro MCP Server exposes 14 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Miro to Claude Desktop via MCP

Follow these steps to integrate the Miro MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Miro

Look for the 🔌 icon in the chat — your 14 tools are now available

Why Use Claude Desktop with the Miro MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Miro through the Model Context Protocol.

01

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Miro + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Miro MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Miro MCP Tools for Claude Desktop (14)

These 14 tools become available when you connect Miro to Claude Desktop via MCP:

01

add_board_member

Requires the board ID and user ID. Optionally set the role (owner, admin, editor, commenter, viewer). The user must already have a Miro account. Add a member to a Miro board

02

create_board

Requires the board name and optionally a description. Returns the created board with its ID, view link and edit link. Create a new Miro board

03

create_card

Requires the board ID and card title. Optionally set a description and x,y position. Cards are structured content widgets with title and description fields. Create a card widget on a Miro board

04

create_comment

Requires the board ID and comment content. Optionally reply to an existing comment by providing its ID as parent_id. Add a comment to a Miro board

05

create_sticky_note

Requires the board ID and the sticky note content (text). Optionally set the x,y position on the canvas. Returns the created sticky note with its ID and position. Create a sticky note on a Miro board

06

delete_board_item

Provide the board ID and item ID. WARNING: this action is irreversible. Delete an item from a Miro board

07

get_board

Provide the board ID (found in the board URL or from list_boards). Get details for a specific Miro board

08

get_board_item

Provide the board ID and item ID. Get details for a specific item on a Miro board

09

get_user_context

Returns user ID, name, email, avatar and account type. Use this to verify your access token is working correctly and to see which user identity the API calls will appear as. Get the authenticated Miro user context

10

list_board_items

) placed on a Miro board. Each item includes its type, ID, content, position, rotation, size and style. Optionally filter by item type (sticky_note, card, shape, text, connector, image, embed, frame, document, mind_map) and set a limit. List items (widgets) on a Miro board

11

list_board_members

Each member shows their user ID, name, email, role (owner, admin, editor, commenter, viewer) and permission level. Optionally set a limit. List members of a Miro board

12

list_boards

Each board includes its ID, name, description, creation date, owner and permissions. Optionally set a limit on the number of results. Use this to discover boards before accessing their content. List Miro boards accessible by the user

13

list_comments

Each comment includes its ID, content text, author info, creation date and parent comment ID (for replies). Optionally set a limit. List comments on a Miro board

14

update_board

Provide the board ID and the new name and/or description. Only provided fields will be updated. Update a Miro board name or description

Example Prompts for Miro in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Miro immediately.

01

"Show me all the sticky notes on my Sprint Planning board."

02

"Create a new board called 'Q2 OKRs' with a description 'Quarterly objectives and key results'."

03

"Add a sticky note to my board saying 'Meeting notes: Discussed API versioning strategy' at position x:100, y:200."

Troubleshooting Miro MCP Server with Claude Desktop

Common issues when connecting Miro to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Miro + Claude Desktop FAQ

Common questions about integrating Miro MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.

Connect Miro to Claude Desktop

Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.