Agiflow MCP 0.0.3 guide

Quick answer

Agiflow MCP 0.0.3 is the current connection contract for exposing scoped project work to compatible AI assistants. Start here for version behavior, then choose a server for the smallest useful access boundary.

What MCP 0.0.3 defines

Give each task only the third-party tools it needs

MCP 0.0.3 can discover actions from organization-connected third-party MCP servers, attach an exact action set to a task, and execute only that approved set from any standard Agiflow MCP scope.

1. 1. Find a suitable action

   Call find_connected_tools from organization, project, or work-unit scope with the user's explicit intent. Follow hasMore with the next offset when more results exist.

2. 2. Attach the smallest set

   Use update_task with exact server IDs and tool names from discovery in mcpTools. The list replaces existing access. Omit it to keep access or pass an empty list to revoke all third-party tools.

3. 3. Verify allowed access

   Call get_task and inspect allowedMcpTools. Each allowed entry includes the input schema needed to build execution arguments.

4. 4. Execute through the task permission

   Use task_exec with the approved server, tool, and schema-compliant arguments. Organization scope also requires projectId and taskId. Project and work-unit scopes require taskId. Task scope infers both. Generated ext__server__tool aliases remain task-scope shortcuts.