Task MCP
Enable Claude to create, manage, and track development tasks with intelligent prioritization and workflow automation.
Overview
Task MCP provides Claude Code with comprehensive task management capabilities within Agiflow's scoped MCP architecture. It enables Claude to create, read, update, delete, move, and reorder tasks while maintaining strict project boundaries and user ownership controls.
As a task-scoped MCP server, it automatically knows the project and task context, providing agent assignment capabilities, status management, and development tracking features. Each task operation respects organizational boundaries and project ownership for secure collaboration.
Available MCP Tools
create-task
Create new tasks with title, description, status, priority, due dates, tags, and agent assignment.
- • Required agent assignment
- • Status and priority management
- • Acceptance criteria support
list-tasks
List tasks with pagination, filtering by status, priority, assignee, and full-text search capabilities.
- • Advanced filtering options
- • Sorting and pagination
- • Search functionality
get-task
Retrieve detailed information about a specific task including all metadata and development info.
- • Complete task details
- • Development metadata
- • Agent session tracking
update-task
Update existing tasks including status changes, reassignment, priority updates, and development tracking.
- • Status transitions
- • Agent reassignment
- • Development info updates
move-task
Move tasks between different statuses (columns) and reposition them within status columns.
- • Status column changes
- • Position management
- • Kanban board support
Additional Operations
Delete tasks, reorder tasks within status, and access task resources for enhanced context.
- • delete-task operation
- • reorder-tasks within status
- • Task and project resources
How Task MCP Works
Scoped Task MCP Server Creation
When Claude connects to a specific task, Agiflow creates a dedicated Task MCP server instance with task-level permissions and automatic task context awareness.
Authentication & Authorization
The MCP server validates user identity, organization membership, and project access before providing task management tools with appropriate member and status context.
Tool Registration
The builder pattern registers task management tools (create, read, update, delete, move, reorder) based on the user's permissions and task context.
Status & Member Resolution
All task operations automatically resolve status names to IDs and member names to member IDs, ensuring Claude can work with human-readable names while maintaining data integrity.
Common Use Cases
Task Creation & Assignment
"Create a new task 'Implement user login' assigned to backend-agent with high priority" - Claude creates tasks with proper agent assignment.
Task Filtering & Search
"List all high priority tasks assigned to frontend-agent in In Progress status" with advanced filtering and search.
Task Status Management
"Move task to Done" or "Update task status to In Progress" with position management for Kanban boards.
Development Tracking
Update tasks with development information, agent sessions, git worktrees, and progress notes.
Task Lifecycle
Created
Task is defined with clear requirements
Planned
Prioritized and scheduled
In Progress
Actively being worked on
Review
Testing and validation
Complete
Delivered and verified
Integrations
Git Integration
Task MCP automatically links tasks to git branches, commits, and pull requests for seamless development tracking.
- • Automatic branch creation for tasks
- • Commit message templates
- • PR linking and status updates
Project Management Tools
Sync with popular project management platforms to maintain consistency across your development stack.
- • Jira integration
- • GitHub Issues sync
- • Linear connection
MCP Context & Authorization
Context Information
The Task MCP automatically receives context information when initialized:
- userId - Authenticated user identifier
- memberId - Organization member identifier
- organizationId - Organization scope boundary
- projectId - Optional project scope (when available)
- taskId - Optional focused task (when available)
- statuses - Available task statuses for the project
- members - Available organization members for assignment
Security & Authorization
- Organizational boundaries enforced via OrganizationDurableObject
- Member and status name resolution for human-readable operations
- Task ownership validation for all operations
- Builder pattern for selective tool registration
- Automatic agent assignment validation
Best Practices
🎯 Clear Task Definition
Write clear, specific task descriptions with concrete acceptance criteria. This helps Claude provide better estimates and track progress accurately.
📊 Regular Updates
Keep task status updated as you work. This improves Claude's ability to provide accurate project insights and timeline predictions.
🔗 Link Related Work
Connect tasks to git branches, commits, and pull requests. This creates a complete audit trail and helps with future planning.