Excalidraw Architect
PYPI · EXCALIDRAW-ARCHITECT-MCP · SCANNED SEP 13
Generate beautiful Excalidraw architecture diagrams with auto-layout and component styling
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 949 tokens (~237/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Excalidraw Architect MCP server?
Excalidraw Architect runs locally as a PyPI package, launched with uvx excalidraw-architect-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · excalidraw-architect-mcp
claude mcp add bv-venky-excalidraw-architect-mcp -- uvx excalidraw-architect-mcp
{
"mcpServers": {
"bv-venky-excalidraw-architect-mcp": {
"command": "uvx",
"args": [
"excalidraw-architect-mcp"
]
}
}
} {
"servers": {
"bv-venky-excalidraw-architect-mcp": {
"command": "uvx",
"args": [
"excalidraw-architect-mcp"
]
}
}
} codex mcp add bv-venky-excalidraw-architect-mcp -- uvx excalidraw-architect-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bv-venky-excalidraw-architect-mcp": {
"type": "local",
"command": [
"uvx",
"excalidraw-architect-mcp"
],
"enabled": true
}
}
} openclaw mcp add bv-venky-excalidraw-architect-mcp --command uvx --arg excalidraw-architect-mcp
mcp_servers:
bv-venky-excalidraw-architect-mcp:
command: "uvx"
args: ["excalidraw-architect-mcp"] {
"McpServers": {
"bv-venky-excalidraw-architect-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"excalidraw-architect-mcp"
]
}
}
} assistant mcp add bv-venky-excalidraw-architect-mcp -t stdio -c uvx -a excalidraw-architect-mcp
{
"mcpServers": {
"bv-venky-excalidraw-architect-mcp": {
"command": "uvx",
"args": [
"excalidraw-architect-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 −3
- Stability: pass → 0.80 functional
- 3 Sept 26 +1
- Stability: 0.97 → pass security
- 1 Sept 26 +1
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 13 Sept 2026 · Analysed pypi/excalidraw-architect-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_diagram Create Diagram ~335
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.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | yes | List of connections. Each dict has: - from_id (str, required): Source node id - to_id (str, required): Target node id - label (str, optional): Edge label text - style (str, optional): "solid", "dashe… |
| direction | string | – | Layout direction - "LR" (left-right), "TD" (top-down), "BT" (bottom-up), "RL" (right-left). Default: "LR" |
| nodes | array | yes | List of nodes. Each dict has: - id (str, required): Unique identifier - label (str, required): Display text - component_type (str, optional): Technology name for auto-styling (e.g., "kafka", "postg… |
| output_path | string | yes | File path to save the .excalidraw file (e.g., "./arch.excalidraw") |
| theme | string | – | Color theme - "default", "dark", "colorful". Default: "default" |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_diagram_info Get Diagram Info ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the .excalidraw file. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mermaid_to_excalidraw Mermaid To Excalidraw ~180
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).
| Name | Type | Req | Description |
|---|---|---|---|
| mermaid_syntax | string | yes | Mermaid flowchart source code. |
| output_path | string | yes | File path to save the .excalidraw file. |
| theme | string | – | Color theme - "default", "dark", "colorful". Default: "default" |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
modify_diagram Modify Diagram ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the existing .excalidraw file. |
| operations | array | yes | Ordered list of operations. Each dict has: - op: "add_node" | "remove_node" | "update_node" | "add_connection" | "remove_connection" For add_node: - id (str): New node identifier - label (… |
| theme | string | – | Color theme for re-rendering. Default: "default" |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Excalidraw Architect MCP server?
Excalidraw Architect is an MCP server listed in the public MCP registry as io.github.BV-Venky/excalidraw-architect-mcp. Generate beautiful Excalidraw architecture diagrams with auto-layout and component styling. This page covers its PyPI package (excalidraw-architect-mcp).
Is the Excalidraw Architect MCP server safe to use?
Excalidraw Architect scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 13 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Excalidraw Architect MCP server expose?
Excalidraw Architect exposes 4 tools: create_diagram, mermaid_to_excalidraw, modify_diagram, get_diagram_info. Their descriptions and schemas cost roughly 918 tokens of context every time the server is loaded.
Is the Excalidraw Architect MCP server still maintained?
Excalidraw Architect is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.