astro-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASTRO_FLOW_URL | No | Base URL of the ComfyUI Astro Flow extension's /astro-flow/v1 API. Defaults to http://127.0.0.1:8188. | http://127.0.0.1:8188 |
| ASTRO_FLOW_TOKEN | No | Optional bearer token. When set, all HTTP requests include 'Authorization: Bearer <token>'. Whether unauthenticated local requests are allowed is decided by the extension. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_capabilitiesB | Search Astro Flow node capabilities. An empty query lists all capabilities. |
| describe_capabilityB | Get one capability's parameter and connection details. |
| list_canvasesA | List currently open Astro Flow workflow canvases. |
| get_workflowA | Read the current nodes, links, and revision of a canvas. |
| edit_workflowA | Apply Astro Flow operations to a canvas at a known revision. Send exactly one operation. Allowed types: add_node, remove_node, set_parameter, connect, disconnect. Supply a unique request_id for idempotency. On revision conflict, read the canvas again before deciding whether to submit another edit. The server validates node types and operation details. |
| submit_workflowB | Submit a canvas for execution at a known revision, using a unique request_id. |
| get_runA | Read a submitted run's status, artifacts, and errors. |
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 targets a distinct resource and action: workflow submission, run status, capability search/describe, canvas listing/reading/editing. There is no overlap in purpose, and descriptions further clarify boundaries.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (submit_, get_, search_, describe_, list_, edit_). The naming is uniform and predictable.
Seven tools is well-scoped for an Astro Flow workflow server, covering execution, monitoring, capability discovery, and canvas editing without unnecessary bloat or thinning.
The core lifecycle is covered: reading/editing canvases, submitting workflows, retrieving run status, and exploring capabilities. A minor gap exists—there is no run listing or cancellation—but it does not break the primary workflows.