Bring Whiteboarding
to VS Code Copilot
Learn how to connect Miro to VS Code Copilot and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Miro MCP Server?
Connect your Miro account to any AI agent and simplify your visual collaboration and whiteboarding workflows through natural conversation.
What you can do
- Board Management — List all collaborative boards, retrieve detailed metadata, and create new boards programmatically
- Visual Content Control — List all items on a board (sticky notes, shapes, text) and place new content directly from your agent
- Member Coordination — Query board members and sharing settings to manage access across your organization
- Operational tracking — Monitor board activity and stay on top of your visual projects
- Direct Whiteboarding — Add sticky notes and ideas to a board without leaving your conversation
How it works
1. Subscribe to this server
2. Enter your Miro Access Token (OAuth 2.0)
3. Start managing your visual collaboration from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Product Managers — organize roadmaps, sprint planning, and user journey maps visually.
- Designers & UX Researchers — manage board items, sticky notes, and brainstorming artifacts directly.
- Agile Teams — automate the creation of project boards and member synchronization.
Built-in capabilities (8)
Create a new Miro board
Add a sticky note to a board
Delete a Miro board
Get details for a specific board
List all items on a board
List board collaborators
List Miro boards
List linked organizations
Why VS Code Copilot?
GitHub Copilot Agent mode brings Miro data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Miro in VS Code Copilot
Miro and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Miro to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Miro in VS Code Copilot
The Miro 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. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Miro for VS Code Copilot
Every tool call from VS Code Copilot to the Miro MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I list all items on a Miro board using my AI agent?
Yes! Use the list_board_items tool and provide the Board ID. Your agent will retrieve all widgets, sticky notes, and text blocks on that board.
How do I add a new sticky note to a board?
Use the create_sticky_note action. Provide the Board ID and the content of your note to place it programmatically on the whiteboard.
Is it possible to manage board members via AI?
Yes, the get_board_members tool allows you to retrieve a list of all users who have access to a specific board, along with their roles.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.