MCP 0.0.2
Agiflow MCP server guide
Choose the smallest organization, project, work unit, or task MCP server. Organization MCP supports OAuth or an API key, while narrower servers use API keys.
Quick answer
Agiflow provides four scoped MCP endpoints. Organization MCP supports OAuth or an API key. Project, work-unit, and task MCP endpoints use API keys. Each endpoint fixes the assistant to one scope in the Agiflow hierarchy, so choose the narrowest endpoint that can complete the work.
Compare the servers
| Server | Fixed boundary | Best for |
|---|---|---|
| Organization MCP | Everything the authenticated API key can access in one Agiflow organization. | Plan across projects |
| Project MCP | One project, including its work units, tasks, artifacts, vault entries, analytics, and workflows. | Run one project board |
| Work Unit MCP | One work unit inside a project, plus the tasks, comments, and artifacts needed to deliver it. | Turn a work unit into deliverable tasks |
| Task MCP | One task, its comments, linked artifacts, and task-enabled external MCP execution. | Keep one task current |
Start with the connection panel
- Open the scope you want to expose. A project uses More then AI connection. A work unit uses Work Unit MCP. A task uses Task MCP.
- Copy the generated endpoint. The URL contains the identifiers that lock the client to the selected scope.
- Create and copy an API key. Add it as an
x-api-keyheader in the client configuration. - Restart the client and verify scope. Use the scope tool before asking the assistant to act.