Excalidraw MCP Server – Interactive AI Diagrams

Overview

Excalidraw's official MCP App server brings the Excalidraw hand-drawn diagram style into compatible AI clients. Instead of returning only text or a static image, the server can stream diagram elements into an interactive embedded interface, support fullscreen viewing and editing, and provide visual feedback to the model so it can refine the result.

What the MCP server enables

The server is designed around standard Excalidraw element JSON and exposes tools that help an AI agent understand the expected format and render diagrams. Documented capabilities include:

• Returning a diagram-format cheat sheet before generation.
• Creating streamed Excalidraw views from standard element JSON.
• Rendering shapes, text, arrows, lines, images, and other supported elements.
• Showing smooth hand-drawn animations as diagram elements arrive.
• Opening diagrams in fullscreen mode for closer inspection and editing.
• Capturing the rendered result as image context so the model can see and improve it.
• Saving and restoring diagram checkpoints so later revisions do not require resending the entire scene.
• Preserving user edits through the checkpoint and local caching workflow.
• Supporting prompts for architecture diagrams, flowcharts, state diagrams, visual explanations, and freeform sketches.

When to use it

Use Excalidraw MCP when a conversation benefits from an editable visual artifact rather than a purely textual answer. Typical workflows include software architecture diagrams, request flows, database relationships, process maps, state machines, infrastructure sketches, product concepts, workshop visuals, and educational explanations.

The server is especially useful in MCP hosts that support MCP Apps, because the diagram can render interactively inside the chat instead of requiring a separate browser or exported image.

Connection and authentication

Excalidraw recommends its hosted remote endpoint:

https://mcp.excalidraw.com

Compatible clients add this URL as a custom MCP server or connector using Streamable HTTP. The official setup does not document an API key, OAuth flow, bearer token, or required environment variable for the hosted endpoint.

The project also supports local installation through a downloadable MCP bundle or by building the official repository and launching its Node.js stdio entry point. This YAML uses only the recommended hosted transport because the local source-build command requires a machine-specific installation path.

Key considerations

The MCP host must support MCP Apps to display the full embedded interactive interface. Diagram input uses standard Excalidraw element JSON rather than the simplified skeleton format, so labels are represented as separate text elements and must be positioned correctly. Remote checkpoint persistence may depend on the server's backing store, and in-memory checkpoints can be lost after a cold start. Users should review generated diagrams for accuracy, layout quality, accessibility, and sensitive information before sharing or exporting them.