Creativity · MCP — server

MCP Mural Server

The MCP Mural Server exposes Mural's REST API so MCP clients can list workspaces and murals, read widgets (sticky notes, shapes, connectors), post new items, and export images. It pairs well with Mural's built-in design thinking templates — letting an LLM drive the 'synthesize' and 'summarize' steps of a workshop.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript
Transports: stdio

Capabilities

Tools: list_murals, create_sticky_note, update_widget, list_widgets, export_mural
Resources: mural://workspace/{id}/mural/{id}
Auth: Mural OAuth 2.0 (murals:read, murals:write)

Install

npx -y @community/mcp-server-mural

Configuration

{
  "mcpServers": {
    "mural": {
      "command": "npx",
      "args": ["-y", "@community/mcp-server-mural"],
      "env": {
        "MURAL_CLIENT_ID": "${MURAL_CLIENT_ID}",
        "MURAL_CLIENT_SECRET": "${MURAL_CLIENT_SECRET}"
      }
    }
  }
}

Frequently asked questions

How does it differ from the Miro MCP server?

Both target collaborative whiteboards. Mural is more common in large enterprises and consulting firms, with strong design-thinking templates. Miro has broader cross-team adoption. The MCP shapes are similar.

Can it work with Mural's AI?

Mural has its own AI features (Mural AI). The MCP server complements them — Mural AI handles in-canvas UX, MCP lets external clients drive the board.

Is rate limiting a concern?

Yes — batched widget creation is often more efficient than per-item calls. Most community servers expose a batch_create_widgets helper.

Sources

Mural Developer Platform — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20
MCP servers repo — accessed 2026-04-20