FlowZap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flowzap_validateA | Validate FlowZap Code syntax. Use this to check if FlowZap Code is valid before creating a playground. |
| flowzap_create_playgroundA | Create a FlowZap playground session with the given code and return a shareable URL. Use this after generating FlowZap Code to give the user a visual diagram. Set view to 'architecture' when user requests an architecture diagram. |
| flowzap_get_syntaxB | Get FlowZap Code syntax documentation and examples. Use this to learn how to write FlowZap Code for workflow diagrams. |
| flowzap_export_graphA | Export FlowZap Code as a structured JSON graph (lanes, nodes, edges). Use this to inspect diagrams structurally, query relationships, or analyze workflow patterns without re-parsing DSL. |
| flowzap_artifact_to_diagramB | Parse real artifacts (HTTP logs, OpenAPI specs, code snippets) into FlowZap Code diagrams. Use this to convert raw technical data into visual workflows that can be explained and refined. |
| flowzap_diffA | Compare two versions of FlowZap Code and get a structured diff showing what changed (nodes/edges added, removed, updated). Use this to explain changes to users. |
| flowzap_apply_changeA | Apply a structured change to FlowZap Code (insert/remove/update nodes or edges). Safer than regenerating entire diagrams - preserves existing structure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: apply_change modifies diagrams, artifact_to_diagram parses data, create_playground generates URLs, diff compares versions, export_graph outputs JSON, get_syntax provides documentation, and validate checks syntax. The descriptions reinforce unique functions, eliminating confusion.
All tools follow a consistent 'flowzap_' prefix with snake_case naming and clear verb_noun patterns (e.g., apply_change, artifact_to_diagram). This uniformity makes the set predictable and easy to navigate, with no deviations in style or structure.
With 7 tools, the server is well-scoped for its diagramming and workflow domain. Each tool earns its place by covering essential operations like creation, validation, comparison, export, and parsing, without being overly sparse or bloated.
The toolset provides complete coverage for the FlowZap diagramming lifecycle: from learning syntax (get_syntax) and validating code (validate) to creating diagrams (artifact_to_diagram), applying changes (apply_change), comparing versions (diff), exporting data (export_graph), and sharing results (create_playground). No obvious gaps exist for the stated purpose.