Miro MCP server for Claude, ChatGPT, Claude Code and Cursor

How to connect Miro

1. 1
   Click Connect Miro free and sign in to Miro.
2. 2
   Add ContextGate to your AI app:

   ClaudeChatGPTClaude CodeCursorGitHub CopilotCodexGemini CLIOther

   1. 1

      In Claude, open Settings → Connectors and click Add custom connector.

   2. 2

      Name it ContextGate and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Click Add, then Connect, and sign in to ContextGate.

   4. 4

      In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.

   The full Claude guide

   1. 1

      In ChatGPT settings, open Apps & Connectors (or Connectors) → Advanced and turn on Developer mode.

   2. 2

      Create a connector, choose OAuth, and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Sign in to ContextGate when ChatGPT redirects you, then pick the connector in a chat.

   The full ChatGPT guide

   1. 1

      Run this in a terminal:

      claude mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      Start Claude Code, run /mcp, choose contextgate and sign in to ContextGate.

   The full Claude Code guide

   Add to Cursor

   1. 1

      Click Add to Cursor, or add this to ~/.cursor/mcp.json:

      {
        "mcpServers": {
          "contextgate": {
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      In Cursor Settings → MCP, sign in to ContextGate when Cursor asks.

   The full Cursor guide

   Add to VS Code

   1. 1

      Click Add to VS Code, or add this to .vscode/mcp.json:

      {
        "servers": {
          "contextgate": {
            "type": "http",
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      Start the server when VS Code asks, sign in to ContextGate, and use it from Copilot Chat in Agent mode.

   The full GitHub Copilot guide

   1. 1

      Run this in a terminal:

      codex mcp add contextgate --url https://api.contextgate.ai/mcp

   2. 2

      Then sign in to ContextGate:

      codex mcp login contextgate

   The full Codex guide

   1. 1

      Run this in a terminal:

      gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      In Gemini CLI, run /mcp auth contextgate and sign in to ContextGate.

   The full Gemini CLI guide

   1. 1

      Add a remote (HTTP) MCP server with this URL:

      https://api.contextgate.ai/mcp

   2. 2

      Apps that support MCP sign-in ask you to sign in to ContextGate the first time they connect.

   3. 3

      An app that can't sign in can use a workspace API key instead: create one under API keys and add ?api_key=<your key> to the URL.

   More on adding it to any MCP app
3. 3
   Ask your AI app to use Miro, then open Activity to see the call.

Miro's own MCP server

• ContextGate now connects to Miro's own MCP server by default: in Add Connection, search for Miro and sign in with your Miro account. There's nothing to copy or paste.
• ContextGate's app connector for Miro is still there, under Ways to connect on the same card.
• Whichever way you connect, your tool switches, policies and Activity work the same.

What you get with Miro and ContextGate

• Your AI apps can use MiroClaude, Cursor, ChatGPT and other AI apps reach Miro through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Miro tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Miro tools

Examples of what your AI apps can do in Miro. You'll see the exact list of tools after you connect it.

• create_boardTool to create a new board. use when you need to set up a board with a specific name, description, and policies. example: "create a new board named project plan".
• update_boardTool to update properties of a specific board. use when you have a board id and need to modify its name, description, or permissions policy. use after confirming the board exists.
• delete_itemTool to delete a specific item from a board. use when you need to remove an item (e.g., shape, sticky note) after confirming its board and item ids.
• update_app_card_itemTool to update an app card item on a board. use when you need to modify properties of an existing app card item. include only fields to change.
• delete_app_card_itemTool to delete an app card item from a board. use when you need to remove an app card item created by your app after it is no longer needed.
• delete_document_itemTool to delete a document item from a board. use when you need to remove a document item (e.g., pdf or image) that is no longer relevant. example: "delete the document item with id 'item456' from board 'board123'."
• get_app_card_itemTool to retrieve a specific app card item by its id. use when you need the details of an existing app card item.
• get_boardTool to retrieve details of a specific board. use when you have a board id and need to fetch its metadata.
• get_board_membersTool to retrieve a list of members for a board. use when you need to list all users with access to a board after confirming its id.
• get_boardsTool to retrieve accessible boards with optional filters. use when you need to list or search boards by team, project, owner, or keywords.
• get_connectorsTool to retrieve a list of connectors on a board. use after confirming the board id and when you need to page through connector items.
• get_tagTool to retrieve details of a specific tag on a board. use when you have a board id and tag id and need its metadata.
• list_organizationsTool to retrieve list of organizations accessible to the user. use when you need to view all available organizations.
• miro_create_app_card_itemTool to add an app card item to a board. use when you need to push a rich preview card with custom fields into a miro board (e.g., after assembling card data).