Mural MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MURAL_CLIENT_ID | Yes | Your Mural app's client ID (required) | |
| MURAL_REDIRECT_URI | No | OAuth redirect URI (defaults to http://localhost:3000/callback) | http://localhost:3000/callback |
| MURAL_CLIENT_SECRET | No | Your Mural app's client secret (optional but recommended) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-workspacesC | List all workspaces the authenticated user has access to |
| get-workspaceC | Get detailed information about a specific workspace |
| test-connectionA | Test the connection to Mural API and verify authentication |
| clear-authA | Clear stored authentication tokens (requires re-authentication) |
| debug-api-responseB | Debug tool: Show raw API response from workspaces endpoint for troubleshooting |
| get-rate-limit-statusB | Get current rate limiting status including remaining tokens and refresh times |
| list-workspace-boardsB | List all boards (murals) within a specific workspace |
| list-room-boardsB | List all boards (murals) within a specific room |
| get-boardC | Get detailed information about a specific board (mural) |
| check-user-scopesB | Check the current user's OAuth scopes and permissions |
| get-mural-widgetsC | Get all widgets from a mural |
| get-mural-widgetB | Get details of a specific widget by ID |
| delete-widgetC | Delete a widget by ID |
| create-sticky-notesC | Create sticky notes on a mural (max 1000 per request) |
| update-sticky-noteC | Update a sticky note widget in a mural |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have distinct purposes, but there is some overlap between 'list-room-boards' and 'list-workspace-boards' that could cause confusion about which to use for listing murals in a specific context. Additionally, 'debug-api-response' and 'test-connection' both serve troubleshooting roles, though their descriptions help differentiate them.
The naming follows a consistent verb-noun pattern with hyphens (e.g., 'get-board', 'list-workspaces'), but there are minor deviations like 'check-user-scopes' (which uses 'check' instead of 'get') and 'debug-api-response' (which includes 'api' in the noun). Overall, the pattern is clear and mostly uniform.
With 15 tools, this server is well-scoped for managing Mural resources such as workspaces, boards, and widgets. Each tool appears to serve a specific function in the domain, and the count aligns with typical MCP servers, providing comprehensive coverage without being overwhelming.
The toolset covers core CRUD operations for murals, widgets, and workspaces, including listing, getting, creating, updating, and deleting. However, there are minor gaps, such as no tool for creating or updating boards/murals directly, and limited widget management beyond sticky notes (e.g., no general widget creation or other types).