F
licenseNot graded
qualityC
maintenanceEnables AI agents to read, watch, and edit live Excalidraw rooms by joining as a socket bot over a self-hosted relay, bypassing browser automation.
-
excalidraw-room-mcp
by bjcoombs
Related Servers
Alternatives to excalidraw-room-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to programmatically control a live Excalidraw canvas through element-level CRUD operations and real-time synchronization. It allows agents to iteratively build, inspect, and refine diagrams while providing visual feedback via screenshots and scene descriptions.2,213 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to collaboratively draw and annotate Excalidraw diagrams in real-time via MCP tools, synced to a browser canvas.9Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically control a live Excalidraw canvas with element-level CRUD operations and real-time synchronization. It supports iterative diagramming through scene descriptions, screenshots, and advanced layout tools for collaborative AI-human workflows.2,213 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manipulate live visual diagrams on an Excalidraw canvas in real-time via MCP tools.4,430 npm14BSD 3-Clause
- AlicenseAqualityCmaintenanceEnables AI agents to programmatically generate, edit, and view Excalidraw diagrams with real-time browser synchronization. It provides a suite of tools for adding shapes, text, and arrows to diagrams through natural language interactions.114,430 npm100MIT
TDQS
A3.9/5.0
Scored across 18 tools
Disambiguation4/5
Most tools target distinct actions (create/join/leave room, add/update/delete elements, wait/list/acknowledge mentions). A few pairs blur: room_status vs poll_room (both status probes) and snapshot_scene vs show_room (both render visuals), plus update_elements vs translate_elements overlap on movement. Descriptions do address these distinctions, but boundaries are not perfectly crisp.
Naming Consistency5/5
All 18 tools use consistent snake_case with a predictable verb_or_noun + resource pattern (open_room, read_scene, delete_elements, wait_for_mention, create_room). No mixing of camelCase or stray conventions. Names are readable and predictable throughout.
Tool Count4/5
18 tools is on the heavier side (16-25 band), but the domain genuinely spans room lifecycle, scene read/write, element CRUD, and a full mention workflow. Each tool maps to a real operation, though a couple of status/render tools could arguably be merged.
Completeness5/5
Full lifecycle coverage: room create/join/leave/open/status, scene read/snapshot/show, element add/add_raw/update/translate/delete, and a complete mention cycle (wait/list/acknowledge/policy). No obvious dead ends for the stated live-collaboration purpose.
Maintenance
ActivityMaintained
ResponsivenessResponsive