doodle
Related Servers
Alternatives to doodle
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA shared whiteboard for you and your AI agent I wanted my AI agent and me to be able to point at the same thing. Any MCP-capable agent can read the canvas, draw on it, drop thought bubbles, animate elements, and react when you sketch something.1MIT
- 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 gradedqualityDmaintenanceEnables AI agents to draw animated, hand-drawn diagrams on a live whiteboard through MCP tools, allowing users to visually explain concepts and edit scenes interactively.49 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to collaboratively read, write, draw, and diagram on a shared real-time whiteboard canvas with live human edits.1MIT
- AlicenseBqualityBmaintenanceOffline whiteboard with a local MCP server: an agent draws and edits shapes, connectors, tables, Mermaid diagrams and icons on a board (27 tools). Works on .inkboard files, or on the board open in the Inkboard desktop app.276Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables visual collaboration with an AI agent on a codebase through a shared drawing canvas, where hand-drawn diagrams are inferred as editable structure over MCP.12 npmMIT
This server cannot be deployed
TDQS
Scored across 4 tools
The four tools have mostly distinct purposes: get_board reads canvas data, show_board opens an interactive view, draw_board writes/draws, and scan_project scans workspace files. get_board and show_board could be confused at first, but the descriptions explicitly separate reading data from displaying a canvas.
All tool names follow a consistent verb_noun snake_case pattern: get_board, show_board, draw_board, scan_project. The convention is predictable and easy to map to each tool's action.
Four tools is a compact, well-scoped set for a shared canvas server. The only concern is that draw_board carries many responsibilities, including drawing and board-library management, which could justify splitting but does not make the overall count inappropriate.
The core lifecycle is covered: reading board data, displaying the board, and drawing or modifying it. Minor gaps exist around explicit object deletion, undo, or clear operations, but draw_board's modification capabilities and library actions cover most practical workflows.