Connect an AI agent (MCP)
Let an AI agent read your workspace's processes, runbooks, workflows and articles, read-only, with a token you control.
An AI agent (a coaching assistant, Claude, ChatGPT, or one your company builds) can read your live processes through Ovenbird's MCP server, the standard way agents connect to tools. It's part of the Business and Enterprise plans.
Create a token
- Owners and admins go to Manage → AI agents.
- Type a name for the agent (for example "Coaching agent"), choose how long it lasts (Expires in 30 days, Expires in 90 days, Expires in 1 year or Never expires; 90 days unless you change it) and click Create token.
- Copy the token straight away: it's shown only once. Give it to whoever sets up the agent, along with the MCP server address shown there (
https://ovenbird.tech/mcp).
The agent sends the token in every request as Authorization: Bearer <token>. It's an MCP server over Streamable HTTP (no sessions).
What the agent can do
| Tool | What it gets |
|---|---|
list_processes | Every live process: name, area, when it applies, version |
search_processes | The processes and steps that match a few words, with step numbers |
get_runbook | A process as numbered steps (Markdown); with a role, also that role's steps |
get_workflow | The structure: stages, steps, owners, decisions and where each path goes, loops, stage rules, plus a Mermaid diagram |
get_article | The process explained in prose ("How it works") or what changed in its latest version |
what_changed | The latest version and a plain-words summary of what changed |
Everything is read-only and only the published version of live processes. The agent sees what those processes say, including any people named in their steps (for example a step owner written as a name rather than a role). It never sees drafts, chats, the member list or anything from other workspaces.
Stay in control
- The list shows each token, who created it, when it was last used and when it expires. Revoke stops it at once.
- An expired token stops working on its expiry date: create a new one and give it to the agent. To keep an agent running without interruption, create the new token before the old one expires.
- A token nobody has used for 30 days or more is flagged "not used for N days". Revoke it if nothing needs it.
- Each read is logged in the workspace's activity.
- At most 120 requests a minute per token.
- An address that sends 20 wrong, expired or revoked tokens within 10 minutes is blocked for 10 minutes.
If the agent can't connect
| Answer | What it means |
|---|---|
| 401 | The token is missing, wrong, expired or revoked. Check it in Manage → AI agents and create a new one if needed |
| 402 | The workspace's plan doesn't include AI agents, or a payment is overdue |
| 403 | The workspace is closed or suspended |
| 429 | Too many requests: more than 120 a minute for this token, or too many failed attempts from this address. Wait and try again |
- Before connecting an agent you don't run yourself, check how it handles your content: it sends what it reads to its own AI provider.
Still stuck? Ask your workspace owner or an admin, or get in touch with us.