Most workflows we see start in an editor: someone is building a feature and realises part of it is an AI workflow. Now the coding agent they are already talking to can build that workflow in Worfilo and call it from their code, without a trip to the browser.
One command to set it up
npx @worfilo/mcp installThe installer finds Claude Code, Cursor, Antigravity, VS Code and Windsurf, adds the Worfilo server to each, and adds a /worfilo-workflows guide that teaches the agent the graph format and node types. It writes no secrets, so the files are safe to commit. Claude Code users can install it as a plugin instead. Every option is on the MCP server page.
From a sentence to a call in your code
Ask for an automation in plain words, for example "when a support email arrives, triage it and open a Linear issue". The agent then works through six steps:
- Discover the node types and the apps, APIs and MCP servers your account has connected.
- Plan a graph and show you the steps before anything is saved.
- Build it as a draft and fix whatever validation finds.
- Test the draft with realistic input and repair nodes that fail.
- Publish a version once you agree.
- Integrate: create an API key that can run only that workflow, put it in your env file, and write the call into your code.
You stay in charge
The first time the agent calls Worfilo, your browser opens. You sign in, see which editor is asking, and choose what it may do. It runs on OAuth 2.1 with PKCE, so the agent never sees your password, and access is split into five permissions: read, write drafts, publish, run, and create API keys.
Publishing, activating a version and creating keys are marked as consequential, so editors ask you before the agent does them. Every connected agent is listed under API keys, in Connected agents, and disconnecting one takes effect at once.
It is still a workflow you can watch
Nothing the agent builds is hidden in your repository. It is an ordinary Worfilo workflow: open it on the canvas to watch runs, replay one that went wrong, tweak a prompt, or keep editing the draft while the published version serves your app. See Publishing and versions.
Open source
The installer, the local bridge and the guide live at github.com/Worfilo/mcp, and runnable examples at github.com/Worfilo/examples. Issues and pull requests are welcome.
Keep reading
- MCP server for Claude Code, Cursor and VS CodeConnect Claude Code, Cursor, Antigravity or VS Code to the Worfilo MCP server, so your coding agent plans, builds, tests and ships AI workflows for you.
- Workflow API: run workflows from your own codeCall a published workflow over HTTP with an API key and its workflow ID, send it input and get its output back, and test it first in the chat playground.
- Publishing and versions: draft vs published workflowsPublish a Worfilo workflow to freeze its draft into a numbered version. Triggers and the workflow API run that version while you keep editing the draft.
Build it on the canvas
Create a free account, describe the workflow or wire it yourself, and run it in the browser.