Create a new Excalidraw diagram from structured node and connection data.

The LLM provides a relationship map - this tool handles layout, styling, and rendering. No need to specify coordinates.

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 ... end

Component types are auto-detected from node labels (e.g., a node labeled "PostgreSQL DB" automatically gets database styling).

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 modifications.

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 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.

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.

Add or update a service in the knowledge graph.

Remove a service and all dependencies touching it.

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.

Remove the dependency from_id -> to_id.

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

Summarize the whole knowledge graph: services, domains, and topology.

Call this before mutating the graph to reason about current state.

Render the entire architecture to an .excalidraw file.

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

Render a service plus everything within depth hops of it.

direction: "downstream" (its dependencies), "upstream" (its dependents), or "both".

Render only the services belonging to one domain.

Import an existing .excalidraw diagram's services into the knowledge graph.

Bootstraps the graph from diagrams you already created with this tool.

Impact analysis: what breaks if service_id fails?

Reports direct dependents, the full transitive upstream blast radius, and what the service itself depends on.

Trace the shortest dependency path between two services.

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

Export the knowledge graph to another format.

Show how the architecture changed since a git ref (default HEAD).

Compares the current knowledge file against its version at ref.

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

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.