Build workflows from your coding agent

Ask for an automation in plain words, for example “when a support email arrives, triage it and open a Linear issue”. The agent then does the whole job in your editor:

1. Discover. Reads the node types and the apps, credentials, APIs and MCP servers the account has connected.
2. Plan. Drafts a graph from a plain description, and shows you the steps before anything is saved.
3. Build. Creates the workflow as a draft and fixes whatever validation finds.
4. Test. Runs the draft with realistic input and reads failing nodes back to repair them.
5. Publish. Publishes a version once you agree, so the API runs it.
6. Integrate. Creates an API key scoped to that workflow, puts it in your env file, and writes the call into your code.

Each workflow is also a normal Worfilo workflow. Open it on the canvas to watch runs, change prompts, or hand it to a teammate.

Run the installer in your project. It finds Claude Code, Cursor, Antigravity, VS Code and Windsurf, adds the Worfilo server to each, and adds the /worfilo-workflows guide. Existing servers are kept, and no secrets are written, so the files are safe to commit.

The command at the top of this page runs it with defaults. These options narrow it down:

npx @worfilo/mcp install --client claude-code,cursor   # choose editors
npx @worfilo/mcp install --scope user                  # every project, not just this repo
npx @worfilo/mcp install --dry-run                     # show the changes, write nothing
npx @worfilo/mcp uninstall                             # remove them again

In Claude Code you can install Worfilo as a plugin instead. It bundles the server and the guide, and updates with the plugin:

/plugin marketplace add Worfilo/mcp
/plugin install worfilo@worfilo

The installer, the bridge and the guide are open source at Worfilo/mcp.

Prefer to edit the config yourself? The server is https://api.worfilo.com/mcp, over Streamable HTTP. Cursor reads .cursor/mcp.json, VS Code .vscode/mcp.json, Antigravity ~/.gemini/antigravity/mcp_config.json and Windsurf ~/.codeium/windsurf/mcp_config.json.

# 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

Antigravity uses the local bridge, which signs in on first use whatever remote sign-in the editor supports. Any editor can use it: pass --bridge to the installer.

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.

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 bridge keeps its tokens on your machine, readable only by you, and manages them with three commands:

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 them

The installer adds a guide that teaches the agent the platform. It covers 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, which 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 agent only sees the tools its permissions allow. Publishing, activating and creating keys are marked as consequential, so editors ask you first.

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. The Workflow API guide covers the request and response in full, and Worfilo/examples has complete clients in TypeScript, Python and curl.