Excalidraw Architect MCP

Findings (2)

• lowLow. Minor, or common in normal tools. Shown for information.
  No manifest declaring network access and environment variables (agent.json)
• lowLow. Minor, or common in normal tools. Shown for information.
  Contacted these domains while starting up (no manifest to compare against)

  pypi.org

Network activity

Tools exposed (26)

• create_diagram

  Create a new Excalidraw diagram of any supported type. Two input modes: 1. **Graph types** (``architecture``, ``flowchart``) - pass ``nodes`` and ``connections``. The tool handles layout, styling, and rendering; no coordinates needed. 2. **Typed diagrams** (every other type) - pass ``diagram

• mermaid_to_excalidraw

  Convert Mermaid flowchart syntax into an Excalidraw diagram. Supports the mermaid flowchart subset that AI agents commonly generate: - Directions: graph TD, LR, BT, RL - Node shapes: [text], {text}, ((text)), ([text]) - Edge types: -->, ---, -.-> ==> with |label| - Subgraphs: subgraph Title ... e

• modify_diagram

  Modify an existing Excalidraw diagram created by this tool. Supports iterative editing: add components, remove nodes, update labels, and rewire connections - without recreating the entire diagram. IMPORTANT: Call get_diagram_info first to understand the current diagram state before making modifica

• get_diagram_info

  Get a structured summary of an existing Excalidraw diagram. Call this BEFORE modify_diagram to understand what nodes and connections currently exist. The summary includes node ids, labels, component types, and the full connection topology.

• export_diagram

  Export an .excalidraw file to SVG or PNG image. Converts an existing .excalidraw diagram into a portable image file without requiring a browser or the Excalidraw application.

• list_diagram_types

  List every supported diagram type with guidance on when to use it. Call this BEFORE create_diagram when the right diagram type isn't obvious. Picking the wrong type is the most common way a diagram fails - a swimlane drawn as a flowchart loses the handoffs that were the point.

• get_diagram_schema

  Get the JSON schema and selection guidance for one diagram type. Call this before passing a `spec` to create_diagram for a type you have not used yet, so the payload matches on the first attempt.

• kg_init

  Create a new architecture knowledge graph file (markdown). The knowledge graph is the persistent source of truth for your system's services and dependencies. Diagrams are rendered *from* it.

• kg_add_service

  Add or update a service in the knowledge graph.

• kg_remove_service

  Remove a service and all dependencies touching it.

• kg_link

  Add a directed dependency: ``from_id`` depends on / calls ``to_id``. Both services must already exist (add them with kg_add_service first). ``style`` is one of solid/dashed/dotted/thick.

• kg_unlink

  Remove the dependency ``from_id`` -> ``to_id``.

• kg_set_domain

  Assign a service to a domain (optionally set the domain's display label).

• kg_info

  Summarize the whole knowledge graph: services, domains, and topology. Call this before mutating the graph to reason about current state.

• kg_render

  Render the entire architecture to an .excalidraw file.

• kg_render_view

  Render a focused diagram of just the given services (induced subgraph).

• kg_render_around

  Render a service plus everything within ``depth`` hops of it. ``direction``: "downstream" (its dependencies), "upstream" (its dependents), or "both".

• kg_render_domain

  Render only the services belonging to one domain.

• kg_import

  Import an existing .excalidraw diagram's services into the knowledge graph. Bootstraps the graph from diagrams you already created with this tool.

• whats_connected_to

  Impact analysis: what breaks if ``service_id`` fails? Reports direct dependents, the full transitive upstream blast radius, and what the service itself depends on.

• kg_path

  Trace the shortest dependency path between two services.

• kg_lint

  Architecture health check: cycles, single points of failure, orphans, dangling references, and (optionally) unowned services.

• kg_export

  Export the knowledge graph to another format.

• kg_diff

  Show how the architecture changed since a git ref (default HEAD). Compares the current knowledge file against its version at ``ref``.

• kg_onboarding_doc

  Generate a human onboarding guide (entry points, hubs, domains) from the graph.

• kg_drift

  Detect drift between the declared architecture and Python imports under ``code_root``. Best-effort: treats each top-level package as a service and infers edges from imports. Reports undocumented and possibly-stale dependencies.