Blitflow
MCP server

Tools

The five Blitflow MCP tools and their parameters.

All tools mirror the API contract exactly — parameters are validated against the same schemas.

Tool naming: the hosted server exposes underscore names (nodes_list) — contract op names use dots (nodes.list), which some MCP clients can't call as tool names. In a client like Claude Code the tools surface as mcp__blitflow__nodes_list etc. The local stdio server registers the raw dotted names.

nodes_list

List or search the node palette. Returns NodeSpec[].

ParameterTypeRequiredDescription
qstringnoFree-text search (id, title, description)
categorystringnoFilter by category
limitintegernoMax results

nodes_get

Fetch one node spec by id — its exact input/output ports, defaults, enum optionValues, and numeric bounds.

ParameterTypeRequiredDescription
idstringyesNode id, e.g. rd-fast

Call this before running a node and build inputs from the returned spec. Guessed enum values fail validation — they are not in the model's memory.

workflows_get

Fetch a published workflow version's canonical definition.

ParameterTypeRequiredDescription
idstringyesPublished <org-slug>/<workflow-slug> address (e.g. acme/sprite-pack) or the workflow's UUID
versionstringnolatest (default), a full semver (2.1.0), or a major (2)

Returns { id, address, version, sequence, workflow } (address is null until the workflow's slug is claimed) — see Versioning.

runs_create

Run a workflow. Provide exactly one of workflow or workflowRef. The tool consumes the run's event stream internally and returns the terminal outputs.

ParameterTypeRequiredDescription
workflowobjectone ofInline workflow definition
workflowRefstringone of<id>@<version> reference — a published address like acme/sprite-pack@2.1.0 (preferred) or a workflow UUID like 8f61e451-…@2.1.0
inputsobjectnoArtifacts keyed by workflow input name
maxCostUsdnumbernoSpend cap in USD — set this on every run

Result: { outputs: Record<string, Artifact> }. If the run fails, the tool returns the run.failed error — read the message; don't loop.

runs_node

Run a single node by id — no workflow needed. Supports model/llm nodes.

ParameterTypeRequiredDescription
nodestringyesNode id
inputsobjectyesKeyed by input port name — scalars for value ports, Artifacts for data ports
maxCostUsdnumbernoSpend cap in USD

Returns { outputs: Record<string, Artifact> }.

Agent playbook

  1. Discovernodes_list with q/category, then nodes_get the candidate. Build inputs strictly from the spec.
  2. Cap spend — always pass maxCostUsd; prefer the cheapest node that clears the quality bar.
  3. Fetch refs — binary outputs are ref artifacts; download the ref URL for bytes, and reuse persisted refs instead of regenerating.
  4. Stop on failure — a run.failed / error result is terminal. Read the message, fix the inputs, then retry deliberately.

On this page