Skip to main content
Miro is a visual collaboration platform for whiteboarding and planning. This page shows you how to connect it as an MCP server in Corunner so your agents can access whiteboard context and planning artifacts.

Connect with Miro

Open the MCP Servers tab in the Corunner web app.

​
Server details

​
Connect Miro

1

Sign in to Corunner

Sign in to Corunner at app.corunner.ai.
2

Open Integrations

Open Integrations in the left sidebar.
3

Select the MCP Servers tab

Select the MCP Servers tab.
4

Find the Miro card

Find the Miro card in the grid.
5

Turn on the Connect toggle

Turn on the Connect toggle. The Connect Miro modal opens.
6

Verify the Server name

Verify the prefilled Server name (Miro by default; rename if you run multiple instances).
7

Verify the Server URL

Verify the prefilled Server URL. Value: https://your-miro-mcp.example.com/mcp.
8

Click Test URL

Click Test URL to confirm the endpoint format is valid and the server responds.
9

Select the authentication method

Select the authentication method (prefilled OAuth).
10

Click Advanced (Optional)

Expand the Advanced (Optional) panel. It contains the Usage guidance field, a free-text instruction that tells agents when and how to use this server. Corunner appends what you enter here to every tool description sent to the agent, so it directly influences when the agent picks Miro over another source. Custom headers are hidden for OAuth servers.
11

Enter Usage guidance

In the Usage guidance field (placeholder: Tell agents when and how to use this server…), describe when this server should be used, which boards or teams to prefer, what needs human approval, and what must not be accessed. Keep it short and imperative. Max 2000 characters. See the next section for a copyable example.
12

Click Connect with Miro

Click Connect with Miro.
13

Authorize with the provider

Corunner redirects the current tab to the provider’s authorization page.
14

Review and approve permissions

Review and approve the requested permissions in the provider consent screen.
15

Return to Corunner

After approval, return to Corunner automatically.
16

Confirm the green Connected badge

Confirm a green Connected badge and an enabled Connected toggle on the Miro card.

​
Configure Usage Guidance

Usage guidance tells Corunner agents when and how to use this server. It is optional but recommended. A good guidance block answers six questions:
  1. When should agents use this server?
  2. What should they retrieve?
  3. Which resources are permitted?
  4. Which resources require approval or should not be accessed?
  5. What must not be accessed?
  6. How should findings be presented?
Never enter secrets in the Usage guidance field. It is plain text guidance, not a credentials store.
Here is a copyable example for Miro:

​
Verify the Connection

After a successful connection, the Miro card shows:
  • A green Connected status pill on the name row.
  • A Connected to <workspace> meta line with relative time (for example, “Connected to Acme 2 hours ago”).
  • A Connected toggle that is enabled.
  • A <N> capabilities button that expands into the capability list.

​
Capabilities

Miro exposes the following capabilities:
  • read boards
  • read items

​
Check Connection Health

Click the Test connection icon (Wi-Fi glyph, next to the Connected toggle) on the Miro card. This runs a live probe:
  • Green check: the endpoint is reachable and credentials are valid.
  • Red warning: the probe failed.
If the probe fails, open Edit configuration to refresh credentials or verify the Server URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the Miro card to update the connection. Editable fields include:
  • Server name
  • Server URL
  • Authentication method and credentials
  • Custom headers (under Advanced, non-OAuth only)
  • Usage guidance
Creating, editing, disconnecting, and observation consent changes are admin-only actions. Members see status and capabilities, but not the toggle or icon actions.
Click the Observation consent icon (brain glyph) on the Miro card. Observation is separate from tool connection: it controls whether Corunner passively reads resources into organizational memory, while capabilities are unaffected even if observation is disabled. Scopes have:
  • Mode: Disabled / Shadow / Active
  • Sensitivity: Standard / Restricted / Excluded
Excluded scopes cannot be enabled.
The precise effect on Memory & Learnings for advanced modes should be confirmed with the Corunner product team if you plan to depend on it in policy.
Observation consent changes are admin-only.

​
Disable or Disconnect

Disconnecting deletes stored credentials for this connection. If you also want to eliminate provider-side OAuth tokens entirely, revoke the OAuth grant from your Miro account settings.

Connect with Miro

Ready to go? Open the MCP Servers tab and turn on the Miro Connect toggle.

Integrations Overview

Browse all available Corunner integrations.

Memory & Learnings

Learn how Corunner builds organizational memory.

Governance

Review policies for access, observation, and consent.