moki-whiteboard
Related Servers
Alternatives to moki-whiteboard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local-first whiteboard MCP server that enables AI agents to create, inspect, and update canvas diagrams and shapes collaboratively via 13 semantic tools.6MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first visual workspace and MCP server for canvases built by people and agents, with a polished editor, extensions, and SQLite persistence.1,132 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to read and write local infinite canvas data via MCP protocol, with support for image generation and web visualization.MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents a live, persistent diagram canvas they can draw on, inspect via screenshots, and refine element by element, then export as editable .excalidraw files to commit alongside code. Supports architecture diagrams and flowcharts through a CLI, MCP tools, or REST API.5,646 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, modify, and share diagrams on a live Excalidraw canvas through MCP tools, supporting shapes, text, arrows, batch operations, and export to shareable links with images.5,646 npm8MIT
- AlicenseAqualityBmaintenanceLets Claude, Codex, Cursor and other MCP clients draw hand-drawn Excalidraw diagrams on a local whiteboard, saving them as real .excalidraw files the agent can inspect, revise and undo. It also provides rendering to PNG, SVG import, and docs so agents can self-serve setup and troubleshooting.1968 npm1MIT
TDQS
Scored across 16 tools
Most tools target distinct board, page, or element operations, but whiteboard_native_edit is very broad and overlaps with whiteboard_update_elements, whiteboard_add_elements, and whiteboard_manage_page_groups. The boundary between whiteboard_manage_pages (which can group pages) and whiteboard_manage_page_groups is also somewhat unclear. Descriptions help, but an agent may still hesitate between native editing and targeted element/page tools.
Every tool uses the whiteboard_ prefix and snake_case, with a predictable verb_noun or resource_action pattern. Variations like whiteboard_delete_board vs. whiteboard_delete_elements are still readable and consistent within the board-level naming domain.
At 16 tools, the surface is slightly above the ideal 3-15 range but remains reasonable for a whiteboard server covering boards, pages, groups, elements, thumbnails, and export. Each tool appears to earn its place, though some consolidation could reduce overlap.
The set covers board CRUD, page management, page groups, element creation/update/alignment/deletion, inspection, thumbnail retrieval, native editing, and export. Minor gaps remain, such as explicit page duplication or dedicated element grouping, but core lifecycle workflows are well covered.