Create workflow diagrams via AI assistants with FlowZap Code validation and playground URLs.
Flowzap MCP server exists for a simple reason — assistants are far more useful when they can act on Flowzap directly instead of describing what you should do. Create workflow diagrams via AI assistants with FlowZap Code validation and playground URLs.
Create workflow, sequence, and architecture diagrams using AI assistants like Claude, Cursor, Windsurf, and 8 other MCP-compatible tools.
FlowZap turns text prompts into triple-view diagrams (Workflow, Sequence & Architecture) using FlowZap Code DSL. It is NOT Mermaid, NOT PlantUML - it is a unique domain-specific language designed for simplicity and AI generation.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Flowzap is connected, these are the calls the assistant has available:
Cursor — Open Settings → Features → MCP Servers → Add Server. Use the same JSON configContinue.dev — Create .continue/mcpServers/flowzap.yaml with: name: FlowZap mcpServers: - name: flowzap command: npx args: ["-y", "flowzap-mcp"]flowzap_validate — Validate FlowZap Code syntaxflowzap_create_playground — Create a shareable diagram URLflowzap_get_syntax — Get FlowZap Code syntax documentationflowzap_export_graph — Export FlowZap Code as structured JSON graph (lanes, nodes, edges) for reasoningflowzap_artifact_to_diagram — Parse HTTP logs, OpenAPI specs, or code into FlowZap diagramsflowzap_diff — Compare two versions of FlowZap Code and get structured diffflowzap_apply_change — Apply structured patch operations (insert/remove/update nodes/edges)Endpoint — MethodAmong the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Flowzap's toolset — Cursor, Continue.dev, flowzap_validate and 7 more — is a fair guide to whether it matches your workflow. It is maintained by flowzap-xyz; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | Open Settings → Features → MCP Servers → Add Server. Use the same JSON config. |
| Continue.dev | Create .continue/mcpServers/flowzap.yaml with: name: FlowZap mcpServers: - name: flowzap command: npx args: ["-y", "flowzap-mcp"] |
| flowzap_validate | Validate FlowZap Code syntax |
| flowzap_create_playground | Create a shareable diagram URL |
| flowzap_get_syntax | Get FlowZap Code syntax documentation |
| 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) |
| Endpoint | Method |
{
"mcpServers": {
"flowzap": {
"command": "npx",
"args": ["-y", "flowzap-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.