2,500+ MCP servers ready to use
Vinkius

Miro MCP Server for VS Code Copilot 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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": {
      "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.

GitHub Copilot Agent mode brings Miro data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Miro MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Miro

Ask Copilot: "Using Miro, help me..."14 tools available

Why Use VS Code Copilot with the Miro MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Miro through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Miro + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Miro MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Miro MCP Tools for VS Code Copilot (14)

These 14 tools become available when you connect Miro to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Miro to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Miro + VS Code Copilot FAQ

Common questions about integrating Miro MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect Miro to VS Code Copilot

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