FlowZap

Welcome to FlowZap, the App to diagram with Speed, Clarity and Control.

🤖 This documentation is optimized for LLM and AI Agent consumption

Version 1.4.3 | Last Updated: May 2026 | Compliance check tool with shareable ephemeral result URLs, strengthened tool descriptions for auto-invocation across all MCP clients, 8 tools total

The FlowZap MCP (Model Context Protocol) Server enables AI agents to create, validate, and share professional Workflow, Sequence and Architecture diagrams using FlowZap Code—a domain-specific language designed for machine-readable diagram generation.

Tip:Use it with the SKILL md file for optimal results!

{ "type": "object", "properties": {} }

{ "type": "object", "properties": { "code": { "type": "string", "description": "FlowZap Code to validate" } }, "required": ["code"] }

✅ FlowZap Code is valid! Stats: - Lanes: 2 - Nodes: 5 - Edges: 4

❌ Validation failed: - Line 3: Unknown shape "oval". Valid shapes: circle, rectangle, diamond, taskbox - Line 5: Edge missing handle syntax. Use: n1.handle(right) -> n2.handle(left)

Purpose:Create a shareable playground URL with the diagram.

When to Use:After validation passes, create a playground to give users an interactive diagram they can view and edit.

{ "type": "object", "properties": { "code": { "type": "string", "description": "FlowZap Code to load in the playground" }, "view": { "type": "string", "enum": ["workflow", "sequence", "architecture"], "description": "Initial view mode. Default: workflow" } }, "required": ["code"] }

✅ Playground created! 🔗 View your diagram: https://flowzap.xyz/playground/abc123?view=architecture The diagram is ready to view and edit. Share this link with anyone!

- Automatically validates code before creating playground
- Returns validation errors if code is invalid
- Playground URLs expire after 60 minutes
- No authentication required to view
- Useview="architecture"for system-level overview of multi-lane diagrams

Purpose:Run automated SOC2, GDPR, and PIPL compliance analysis on a FlowZap Code data-flow diagram.

When to Use:When the user asks for a privacy, security, or regulatory review of a data-flow diagram. Backed by Deepseek LLM.

{ "type": "object", "properties": { "code": { "type": "string", "maxLength": 50000 }, "lng": { "type": "string", "enum": ["en", "fr", "zh"], "default": "en" } }, "required": ["code"] }

Output:Markdown audit report covering SOC2 CC-series controls, GDPR articles, and PIPL chapters with risks, recommendations, and a link to the manual checker atflowzap.xyz/soc2-gdpr-pipl-compliance-checker.

✓ UTF-8 plain text only (no emojis) ✓ Node IDs: n1, n2, n3... (globally unique, sequential, no gaps) ✓ Shapes: circle, rectangle, diamond, taskbox ✓ Attributes: label, owner, description, system ✓ Comments: Only "# Display Label" on the same line as the lane opening brace ✓ Sequence view: alternate cross-lane request and response edges in real chronological order ✗ No Mermaid, PlantUML, or other DSL syntax

laneName { # Lane Display Name n1: circle label:"Start" n2: rectangle label:"Process" n1.handle(right) -> n2.handle(left) }

# Basic edge n1.handle(right) -> n2.handle(left) # Edge with label n2.handle(bottom) -> n3.handle(top) [label="Yes"] # Cross-lane edge (prefix with lane name) n3.handle(right) -> fulfillment.n4.handle(left) [label="Send"]

- Must be inside a lane block
- Cannot be nested
- Should reference at least 2 nodes

sales { # Sales Team n1: circle label:"Order Received" n2: rectangle label:"Validate 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"] }

- Step 1: Learn Syntax
{"name": "flowzap_get_syntax", "arguments": {}}}
- Step 2: Generate Code
Based on user request, generate FlowZap Code following the syntax rules.
- Step 3: Validate
{"name": "flowzap_validate", "arguments": {"code": "..."}}
- Step 4: Fix Errors (if any)
Parse error messages and correct the code.
- Step 5: Create Playground
{"name": "flowzap_create_playground", "arguments": {"code": "..."}}
- Step 6: Present to User
Share the playground URL with the user.

For agents that prefer direct HTTP calls instead of MCP:

{ "code": "process { # P n1: circle label:\"Start\" }" }

{ "valid": true, "errors": [], "warnings": [], "stats": { "lanes": 1, "nodes": 1, "edges": 0, "loops": 0 } }

URL:https://flowzap.xyz/api/playground/create

Rate Limit:5 requests/minute, 50/day per IP

{ "code": "process { # P n1: circle label:\"Start\" }" }

{ "url": "https://flowzap.xyz/playground?session=abc123" }

The FlowZap MCP Server works withany tool that supports the Model Context Protocol (MCP). Here is the complete list of compatible tools:

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

All tools use the same JSON configuration format:

{ "mcpServers": { "flowzap": { "command": "npx", "args": ["flowzap-mcp@1.4.3"] } } }

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

- •Syntax Documentation:https://flowzap.xyz/flowzap-code
- •Interactive Playground:https://flowzap.xyz/playground
- •Template Library:https://flowzap.xyz/templates
- •Public MCP Usage Stats:https://flowzap.xyz/.well-known/flowzap-stats.json
- •npm Package:https://www.npmjs.com/package/flowzap-mcp
- •GitHub Repository:https://github.com/flowzap-xyz/flowzap-mcp
- •Official MCP Registry:https://registry.modelcontextprotocol.io/?q=flowzap
- •Smithery Server:https://smithery.ai/server/@flowzap/flowzap
- •Smithery Skill:https://smithery.ai/skills/Flowzap/diagram-skill
- •PulseMCP:https://www.pulsemcp.com/servers/flowzap
- •Glama:https://glama.ai/mcp/servers/flowzap-xyz/flowzap-mcp
- •MCPServers.org:https://mcpservers.org/servers/flowzap-xyz-docs-mcp
- •AIBase:https://mcp.aibase.com/server/1639702939289526535
- •Agent Skill (skills.sh):https://skills.sh/flowzap-xyz/flowzap-mcp/flowzap-diagrams
- •Skill Source:https://github.com/flowzap-xyz/flowzap-mcp/tree/main/skills/flowzap-diagrams
- •Hugging Face Dataset:https://huggingface.co/datasets/Jules-OC/flowzap-sequence-workflows/tree/main

This documentation is optimized for LLM consumption. For human-readable guides, visitflowzap.xyz/flowzap-code

Search Apple's Developer Documentation with smart search and wildcard support.