Skip to content
Back to index

Connect Assistants

This guide shows you how to connect ChatGPT, Claude, Cursor, or another compatible assistant to the right Agiflow resource scope.

01 β€” Choose A Scope

If you want broad workspace help, use the organization endpoint. If you want the assistant to focus on one piece of work, use a project, work-unit, or task endpoint generated from the project board.

Organization

/api/v1/organizations/YOUR_ORG_ID/mcp

Use when the assistant should help across the workspace.

Project

/api/v1/organizations/YOUR_ORG_ID/projects/YOUR_PROJECT_ID/mcp

Use for one project board and its tasks, work units, artifacts, vault entries, and workflows.

Work unit

/api/v1/organizations/YOUR_ORG_ID/projects/YOUR_PROJECT_ID/work-units/YOUR_WORK_UNIT_ID/mcp

Use for one feature, milestone, or epic inside a project.

Task

/api/v1/organizations/YOUR_ORG_ID/tasks/YOUR_TASK_ID/mcp

Use for one task and its comments.

02 β€” Add The Endpoint

Paste the endpoint into your assistant connection settings. This organization example uses the direct API endpoint; scoped project, work-unit, and task URLs follow the same pattern.

Assistant connection settings
{ "mcpServers": { "agiflow": { "url": "https://api.agiflow.io/api/v1/organizations/YOUR_ORG_ID/mcp" } } }
πŸ’‘ Generated URLs:

The project board generates project, work-unit, and task connection URLs for you. Copy those URLs from the relevant project-board connection panel when you want narrower access.

Common config locations

ChatGPT

Add a remote MCP server in ChatGPT connector settings.

Claude

Add the server to your Claude MCP configuration.

Cursor

Add the server under Cursor MCP settings.

03 β€” Authorize Access

Browser authorization

Recommended

Interactive assistants open a browser consent flow. The selected organization and resource become the scope for that assistant session.

API key

Headless tools can use an API key from workspace settings. Keys are validated by hash, expiry, enabled state, user identity, and organization scope.

Optional header
"headers": { "Authorization": "Bearer YOUR_ACCESS_KEY" }

04 β€” Verify The Connection

Ask: "What is my current Agiflow scope?" The assistant should use get_current_scope.

Ask: "List my projects." Organization-scoped sessions should return project records.

Ask: "List tasks for this project." Project-scoped sessions should return tasks for only that project.

Ask: "What capabilities are available?" The assistant should use describe_capabilities before deeper work.

πŸ’‘ OAuth resource endpoint:

Some clients use the default OAuth resource endpoint /api/v1/mcp. During consent, Agiflow binds that session to the resource you select.

Need the exact tool list?

Use the capability reference after setup to see which tools, prompt skills, artifacts, vault entries, and workflow locks are available for each scope.

Support

Need help getting a board connected to your assistant?

Email support

Feedback

Missing a guide for your team’s project setup?

Open an issue

Community

Share how your team plans campaigns, deals, and client work.

Join Discord