Updated September 28, 2026
Build workflows from your coding agent
The Worfilo MCP server lets Claude Code, Cursor, Antigravity and VS Code plan AI workflows, build and test them, publish them, and wire them into your codebase. You describe the automation, the agent does the rest, and you approve each step that matters.
- $npx @worfilo/mcp install --client claude-code
- Added Worfilo to Claude Code
- > Build a workflow that triages new GitHub issues into Linear
- list_node_types 14 types
- create_workflow issue-triage (4 nodes)
- validate_workflow no issues
- run_workflow succeeded, Linear issue LIN-482 created
Connect in a minute
Pick your coding agent. The steps below change to match.
- 1
Run the installer in your project
npx @worfilo/mcp install --client claude-codeIt adds Worfilo to Claude Code and installs the
/worfilo-workflowsguide. Existing servers are kept and no secrets are written, so the files are safe to commit. Or install it as a plugin below. - 2
Sign in once
The first time your agent calls Worfilo, your browser opens. Check which editor is asking and choose what it may do. The agent never sees your password.
- 3
Ask for a workflow
“Build a workflow that triages new GitHub issues into Linear.”
Run one of these in a terminal: the first for every project, the second for this repo only.
# every project
claude mcp add --transport http --scope user worfilo https://api.worfilo.com/mcp
# or this repo only, shared through .mcp.json
claude mcp add --transport http --scope project worfilo https://api.worfilo.com/mcp/plugin marketplace add Worfilo/mcp
/plugin install worfilo@worfiloWhat your agent does
Ask for an automation in plain words. The agent then does the whole job in your editor, and each workflow is also a normal Worfilo workflow you can open on the canvas.
- 1Discover
Reads the node types and the apps, credentials, APIs and MCP servers the account has connected.
- 2Plan
Drafts a graph from a plain description, and shows you the steps before anything is saved.
- 3Build
Creates the workflow as a draft and fixes whatever validation finds.
- 4Test
Runs the draft with realistic input and reads failing nodes back to repair them.
- 5Publish
Publishes a version once you agree, so the API runs it.
- 6Integrate
Creates an API key scoped to that workflow, puts it in your env file, and writes the call into your code.
Permissions, tools and the guide
The details, one at a time.
The first time the agent calls Worfilo, your browser opens. Sign in, check which editor is asking, and choose what it may do. Everything runs over OAuth 2.1 with PKCE, so the agent never sees your password.
workflows:readAlways onSee workflows, node types, connections and credential names. Always on.workflows:writePlan, create and edit draft workflows.workflows:publishPublish versions and choose the active one.runs:writeRun workflows and read their results.api_keys:writeCreate API keys limited to chosen workflows.
Access tokens last an hour and refresh themselves. To see and disconnect every agent, go to API keys, under Connected agents. Disconnecting takes effect at once.
The agent only sees the tools its permissions allow. Publishing, activating and creating keys are marked as consequential, so editors ask you first.
| Tool | Permission | Returns |
|---|---|---|
list_node_typesget_node_type | Read | Every node type, then one type's ports and config schema |
list_integrations | Read | Connected apps and their actions, credentials by name, custom APIs, MCP servers |
list_workflowsget_workflow | Read | Workflows, their draft graph and published versions |
plan_workflow | Write drafts | A drafted graph and readable steps, not saved |
create_workflowupdate_workflow | Write drafts | Save a draft and get validation issues back |
validate_workflow | Read | The same checks publishing runs |
publish_workflowactivate_version | PublishAsks first | Ship a version, or roll back to an earlier one |
run_workflowget_run | Run | Run the draft or the published version and read the output |
create_api_key | KeysAsks first | A key that can run only the workflows named |
get_integration_snippet | Read | TypeScript, JavaScript, Python or curl code for the public API |
The installer adds a guide that teaches the agent the platform: the graph format, the node types, templates, branching, and the steps from plan to integration, so the workflows it builds pass validation the first time.
- Claude Code
- A skill, /worfilo-workflows, that also loads by itself when you ask for an automation.
- Cursor
- The /worfilo-workflows command, plus a rule the agent pulls in when it is relevant.
- Antigravity
- The /worfilo-workflows workflow, plus a rule.
- VS Code
- The /worfilo-workflows prompt in agent mode.
Every MCP client also gets the guide as the design_workflow prompt, even without the installer. Print it with npx @worfilo/mcp skill.
The local bridge keeps its tokens on your machine, readable only by you. It suits any editor without remote sign-in, and three commands manage it. The installer, the bridge and the guide are open source at Worfilo/mcp.
npx @worfilo/mcp login # sign in ahead of time
npx @worfilo/mcp status # see what this machine may do
npx @worfilo/mcp logout # revoke the tokens and forget themThe server itself is https://api.worfilo.com/mcp, over Streamable HTTP. More installer options: --client claude-code,cursor to choose editors, --scope user for every project, --dry-run to show the changes, and uninstall to remove them.
Calling the workflow from your code
A published workflow is an HTTP endpoint. The agent creates a key that can run only that workflow, and writes it to your env file as WORFILO_API_KEY. It then adds a call to POST /v1/workflows/{id}/runs that suits your stack and handles both a finished run and one still in progress.