Schema | Mural MCP Server

Mural MCP Server

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)

Server capabilities have not been inspected yet.

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cogell/mural-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server