MCP server
Connect AI agents to BlitFlow via the Model Context Protocol.
BlitFlow speaks the Model Context Protocol, so AI agents — Claude Code, Claude Desktop, Cursor, or anything MCP-capable — can discover nodes, inspect workflows, and run them as tools. The tools map one-to-one onto the API contract: same operations, same schemas.
Hosted server (recommended)
The hosted server lives at:
https://mcp.blitflow.comIt uses streamable HTTP transport and OAuth — your MCP client opens a browser to sign you in; there are no tokens to paste.
claude mcp add --transport http blitflow https://mcp.blitflow.comLocal server (stdio)
The CLI also serves MCP over stdio via blitflow mcp — useful for
headless environments or when pointing at a non-production API host. It
authenticates like every other CLI command: the session saved by
blitflow login, or a personal access token in
BLITFLOW_TOKEN (which takes precedence).
| Env var | Required | Description |
|---|---|---|
BLITFLOW_TOKEN | no* | Your blit_… token (*unless already logged in) |
BLITFLOW_URL | no | Override the API base URL |
{
"mcpServers": {
"blitflow": {
"command": "npx",
"args": ["-y", "blitflow", "mcp"],
"env": {
"BLITFLOW_TOKEN": "blit_..."
}
}
}
}On a machine where you've already run blitflow login, drop the env block
entirely.
What the agent can do
| Tool | Scope | Purpose |
|---|---|---|
nodes_list | read | Search the node palette |
nodes_get | read | Read one node's exact inputs and enum values |
workflows_get | read | Fetch a published workflow definition |
runs_create | run | Run a workflow (inline or by <id>@<version>) |
runs_node | run | Run a single node |
See Tools for full parameter schemas, and note that
run-scoped tools spend money from the organization's prepaid balance —
there is no per-run cap, so agents should know a node's cost before running it.
Tool results come back as JSON text. On failure a tool returns an error result with the message — agents should read it and adjust, not retry blindly.