Create workflow, sequence, architecture, and mind map diagrams via AI assistants.
Create workflow, sequence, architecture, and mind map diagrams using AI assistants like Claude, Cursor, Windsurf, and 8 other MCP-compatible tools.
FlowZap is a visual workflow diagramming tool with a text-based DSL called FlowZap Code. This MCP server lets AI assistants create diagrams for you.
FlowZap turns text prompts into quad-view diagrams (Workflow, Sequence, Architecture & Mind Map) using FlowZap Code DSL. It is NOT Mermaid, NOT PlantUML - it is a unique domain-specific language designed for simplicity and AI generation.
Key Facts:
circle, rectangle, diamond, taskboxlabel:"Text"[label="Text"]n1.handle(right) -> n2.handle(left)laneName { # LabelThe FlowZap MCP Server works with any tool that supports the Model Context Protocol (MCP):
| Tool | How to Configure |
|---|---|
| Claude Desktop | Add to claude_desktop_config.json:macOS: ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows: %APPDATA%\Claude\claude_desktop_config.json |
| Claude Code | Run: claude mcp add --transport stdio flowzap -- npx -y flowzap-mcpOr add to .mcp.json in your project root. |
| Cursor | Open Settings → Features → MCP Servers → Add Server. Use the same JSON config. |
| Windsurf IDE | Add to ~/.codeium/windsurf/mcp_config.json |
| OpenAI Codex | Add to ~/.codex/config.toml:[mcp_servers.flowzap]command = "npx"args = ["-y", "flowzap-mcp"]Or run: codex mcp add flowzap -- npx -y flowzap-mcp |
| Warp Terminal | Settings → MCP Servers → Click "+ Add" → Paste the JSON config. |
| Zed Editor | Add to settings.json:{"context_servers": {"flowzap": {"command": "npx", "args": ["-y", "flowzap-mcp"]}}} |
| Cline (VS Code) | Open Cline sidebar → MCP Servers icon → Edit cline_mcp_settings.json |
| Roo Code (VS Code) | Add to .roo/mcp.json in project or global settings. |
| Continue.dev | Create .continue/mcpServers/flowzap.yaml with:name: FlowZapmcpServers: - name: flowzap command: npx args: ["-y", "flowzap-mcp"] |
| Sourcegraph Cody | Add to VS Code settings.json via openctx.providers configuration. |
Not Compatible: Replit and Lovable.dev only support remote MCP servers via URL. Use the Public API instead.
All tools use the same JSON configuration format:
{
"mcpServers": {
"flowzap": {
"command": "npx",
"args": ["-y", "flowzap-mcp"]
}
}
}
Windows Users: If tools don't appear, use the absolute path:
"command": "C:\\Program Files\\nodejs\\npx.cmd"Find your npx path with:
where.exe npx
| Tool | Description |
|---|---|
flowzap_validate | Validate FlowZap Code syntax |
flowzap_fix | Deterministically repair mechanical FlowZap Code errors (numbering, inferred handles, label syntax, missing lane labels, emoji/control chars) and return the repaired code plus the corrections applied |
flowzap_create_playground | Create a shareable diagram URL |
flowzap_get_syntax | Get FlowZap Code syntax documentation |
| Tool | Description |
|---|---|
flowzap_export_graph | Export FlowZap Code as structured JSON graph (lanes, nodes, edges) for reasoning |
flowzap_artifact_to_diagram | Parse HTTP logs, OpenAPI specs, or code into FlowZap diagrams |
flowzap_diff | Compare two versions of FlowZap Code and get structured diff |
flowzap_apply_change | Apply structured patch operations (insert/remove/update nodes/edges) |
| Tool | Description |
|---|---|
flowzap_compliance_check | Run automated SOC2, GDPR, and PIPL compliance analysis on a FlowZap Code data-flow diagram. Backed by Deepseek LLM with strict rate limits (3/day per IP, 1/hour burst, global 5-min circuit breaker). Returns a shareable ephemeral result URL (60-min TTL). |
| Tool | Description |
|---|---|
flowzap_mindmap_validate | Validate FlowZap Code syntax and mind-map readiness |
flowzap_mindmap_approve | Check if code is suitable for Mind Map rendering (diamonds/taskboxes = ERROR) |
flowzap_mindmap_template | Generate a ready-to-extend Mind Map tree skeleton |
flowzap_mindmap_create_playground | Create a playground URL with ?view=mindmap |
Ask your AI assistant:
Parse HTTP Logs into Diagrams:
"Here are my nginx access logs. Create a sequence diagram showing the request flow."
The agent uses flowzap_artifact_to_diagram with artifactType: "http_logs".
Analyze Diagram Structure:
"Which steps in this workflow touch the database?"
The agent uses flowzap_export_graph to get a JSON graph, then queries it.
Show What Changed:
"I updated the workflow. What's different from the previous version?"
The agent uses flowzap_diff to compare old and new code.
Safe Incremental Updates:
"Add a logging step after the API call in this diagram."
The agent uses flowzap_apply_change with a structured patch instead of regenerating.
Repair Invalid Code:
"My FlowZap Code fails validation. Fix the mechanical errors for me."
The agent uses flowzap_fix to deterministically repair numbering, inferred handles, label syntax, lane labels, emoji and control characters, then validates the repaired code. Anything the repairer cannot fix is reported as-is — it never invents content.
Compliance Audit:
"Check my data flow diagram for SOC2, GDPR, and PIPL compliance."
The agent uses flowzap_compliance_check to run an automated audit and returns a shareable result page.
Mind Map Creation:
"Create a mind map about AI agent architecture"
The agent uses flowzap_mindmap_template to generate a skeleton, then validates and creates a playground with ?view=mindmap.
The assistant will:
sales { # Sales Team
n1: circle label:"Order Received"
n2: rectangle label:"Submit Order"
n5: rectangle label:"Receive decision"
n1.handle(right) -> n2.handle(left)
n2.handle(bottom) -> fulfillment.n3.handle(top) [label="Submit"]
}
fulfillment { # Fulfillment
n3: rectangle label:"Review Order"
n4: rectangle label:"Return decision"
n3.handle(right) -> n4.handle(left)
n4.handle(top) -> sales.n5.handle(bottom) [label="Approved"]
}
These endpoints are available for external integrations (no authentication required):
| Endpoint | Method | Rate Limit | Description |
|---|---|---|---|
/api/validate | POST | 30/min | Validate FlowZap Code syntax |
/api/fix | POST | 30/min | Deterministically repair mechanical FlowZap Code errors and return the repaired code + applied corrections |
/api/playground/create | POST | 5/min, 50/day | Create ephemeral playground URL (15-min TTL) |
/api/compliance-check | POST | 5/min, 30/day | Run SOC2/GDPR/PIPL compliance analysis on FlowZap Code. Returns frameworks + shareable result URL (60-min TTL). Backed by Deepseek LLM. |
Install the FlowZap skill for 40+ compatible coding agents via skills.sh:
npx skills add flowzap-xyz/flowzap-mcp
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y flowzap-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-flowzap-xyz-flowzap": {
"command": "npx",
"args": [
"-y",
"flowzap-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceflowzap-mcpnpmio.github.flowzap-xyz/flowzap works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.