A
licenseB
qualityD
maintenanceMCP server for the Mural visual collaboration platform enabling board content editing with sticky notes, shapes, text boxes, areas, images, connectors, plus navigation and mural management.
20
20 npm
2
MIT
Mural MCP
Related Servers
Alternatives to Mural MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for controlling Miro whiteboards with AI assistants. Create and manage stickies, shapes, frames, connectors, and more.8826MIT
- AlicenseBqualityCmaintenanceMiro MCP server, exposing all functionalities available in official Miro SDK.97190 npm66Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server for interacting with Mattermost workspaces, providing tools to manage channels, messages, threads, reactions, and user profiles via the Mattermost REST API.-
- FlicenseNot gradedqualityBmaintenanceAn MCP server for Miro that provides 31 tools to interact with Miro boards, enabling board search, reading, layouts, diagrams, and more via public Miro APIs.-
- AlicenseNot gradedqualityDmaintenanceThis repository contains an implementation of an Miro Universal MCP (Model Context Protocol) server. It provides a standardized interface for interacting with Miro's tools and services through a unified API.1MIT
TDQS
A3.6/5.0
Scored across 23 tools
Disambiguation5/5
Each tool targets a distinct resource and action: workspace, room, mural, and specific widget types (sticky note, shape, title, textbox, arrow, area, comment). The list/get/create/update/delete operations are clearly separated, and even similarly named tools like get_mural_widgets vs get_mural_widget are unambiguous.
Naming Consistency4/5
The overall pattern is consistent verb_noun (list_* get_* create_* update_* delete_*). Minor deviations include plural create_sticky_notes/create_shapes vs singular create_arrow/create_area, and generic delete_widget vs delete_mural, but these are readable and predictable.
Tool Count3/5
With 23 tools, the set is on the heavy side but appropriate for the domain, covering mural CRUD plus multiple widget types. It feels slightly bloated because widget creation/update could potentially be consolidated, but each tool serves a distinct purpose.
Completeness4/5
The core lifecycle for murals and widgets is well covered: list/get/create/update/delete for murals, and get/create/update/delete for widgets. Missing workspace/room creation and a few niche widget operations are minor gaps that agents can work around.
Maintenance
ActivityInactive
ResponsivenessNo issues