How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Miro Admin logo. Miro Admin MCP server connector.

Miro Admin MCP Server

List Miro Enterprise organization members (email, role, license, and active status) and remove a member from a team. Removing someone from a team does not by itself change their organization license. Requires a Company Admin OAuth app.

ToolsTools
4
Last updatedLast Updated
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Miro Admin MCP Server?

The Miro Admin MCP server gives AI agents structured, permission-aware access to Miro Admin through the Model Context Protocol. With 4 pre-built actions, agents can read, create, and update Miro Admin data on behalf of authorized users.

Willow ships the Miro Admin MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Miro Admin is being used by every AI agent in your stack.

Tools

List Members

List Miro Enterprise organization members with email, role, license, and active status. Requires a Company Admin token. Page with cursor and limit (max 100).

Get Member

Retrieve one Miro Enterprise organization member by id, including email, license, role, and active status.

List Teams

List teams in the Miro Enterprise organization. Use team id with Remove Team Member. Page with cursor and limit.

Remove Team Member

Remove a member from a Miro team (DELETE /v2/orgs/{org_id}/teams/{team_id}/members/{member_id}). This does not deactivate the organization account and does not change the organization license. Org-level license downgrade is not available through this API.

Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Miro Admin MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-miro-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/miro-admin"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-miro-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/miro-admin"
    }
  }
}

Claude Code

CLI
claude mcp add willow-miro-admin --transport http https://<org>.mcp-s.com/mcp/mcp/miro-admin

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/miro-admin",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Miro Admin

Willow adds the layer Miro Admin and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Miro Admin MCP Server FAQ

What is the Miro Admin MCP server?

The Miro Admin MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Miro Admin data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Miro Admin MCP server different from the official one?

The official Miro Admin MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Miro Admin MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Miro Admin MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Miro Admin, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Miro Admin actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Miro Admin MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Miro Admin MCP locally, you'll see it.

What does the Miro Admin MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Miro Admin MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.