Guide workflows
Your guides already explain how to get a job done with your API. Guide workflows turns those steps into a tool an agent can run and a prompt a person can use, so you don't have to write the same thing twice.
Making workflows
In MCP Studio, under Guide workflows, press Make a workflow from every published guide, or make one from a single guide. Each becomes a chained tool and a prompt, staged for review like any other change. Nothing reaches agents until you publish.
How a guide is read
The generator looks for the API calls in your guide:
- Links to endpoint pages
- Request samples in curl, HTTP,
fetch,requestsand SDK calls - Mentions like
POST /payments
It lists them under Calls in order. If the guide makes no calls a tool can, you get only a prompt.
What stays out of the tool
Optional calls and branches don't go into the tool, because a chained tool always runs its steps in order. Anything like "if the customer is new, also call this" stays as text for the agent to read.
When it isn't sure
Where the generator can't tell what your guide means, it asks you under What to check. Pick what this means for each one, or choose Ask AI to answer these, which chooses from the same options. The workflow is then read again with your answers.
Editing a workflow
Choose Edit tool to change it by hand, with the same editor as any chained tool. When the guide changes, Update from guide reads it again and shows Your edits kept.
The tool's name is set when it's first generated, so renaming your guide doesn't rename a tool agents already use.
Keeping them current
A workflow doesn't change on its own when its guide does. To catch one that has fallen behind, run octri mcp workflows --stale in CI. It exits with an error when any workflow is out of date.
Writing guides that convert well
Put the calls in the order they run.
Link to the endpoint page, or show a real request sample.
Keep optional steps in their own section, in words.
See writing guides.