Taskfolk MCP
MCP serverProductivityThis app adds project management to your AI. Once it is added, your AI can help organize projects, tasks, and shared work for your team. It is designed for teams and their AI agents to work together on day-to-day planning.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the app, then tell your AI which projects or tasks you want it to manage. Start with one project and let your AI help organize the work for your team.
Then ask your AI: use Taskfolk MCP
What your AI can do with it
- Organize team projects in one place
- Create and manage tasks
- Track progress on shared work
- Keep project plans up to date
- Coordinate work across a team
From the project's README
As published by taskfolk/mcp in README.md.
Hosted MCP server for Taskfolk: project management for teams and AI agents.
An agent joins as a named workspace member. It reads the live board, claims tickets, comments, and moves status. Humans see that work on the Agents hub the same way they see a teammate.
- Endpoint:
https://taskfolk.ai/api/mcp/v1(Streamable HTTP) - Official registry:
ai.taskfolk/mcp - Server card: https://taskfolk.ai/.well-known/mcp/server-card.json
- Auth: Bearer API key, or OAuth 2.0 + PKCE
- Support: hi@taskfolk.ai
This repo is the public listing for the hosted server. There is no local install binary. Point your client at the URL.
Connect in Taskfolk first
- Open your workspace sidebar, then Agents.
- Click Connect agent. You need owner, admin, or member (the
agent.connectpermission). Viewers and guests cannot connect. - Name the agent like a teammate seat, for example
Omar's Claude Code. - Pick the tool it actually runs on (Claude Code, Cursor, Codex, and others). The tile is a label and logo only. Every provider gets the same key and the same MCP endpoint.
- Copy the API key immediately. Taskfolk shows the full key once. After that the directory only shows the prefix. Lose it and you disconnect and reconnect.
- Agents do not count as billed seats. Cap is 25 live agents per workspace.
Full walkthrough: How to connect an AI agent
Claude Code
The Connect dialog and the Developer → Skills tab both give you this line. Swap in the full key, not the prefix.
claude mcp add taskfolk-product \
https://taskfolk.ai/api/mcp/v1 \
--header "Authorization: Bearer YOUR_API_KEY"
That registers the hosted server over Streamable HTTP. It does not drop a SKILL.md file.
Cursor
Paste into ~/.cursor/mcp.json:
{
"mcpServers": {
"taskfolk-product": {
"url": "https://taskfolk.ai/api/mcp/v1",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Or pull the generated snippet:
curl -fsSL "https://taskfolk.ai/api/skill/cursor.mcp.json?workspace=YOUR_SLUG" \
-H "Authorization: Bearer $TASKFOLK_API_KEY" \
-o ~/.cursor/mcp.json
VS Code
Paste into .vscode/mcp.json in the workspace:
{
"servers": {
"taskfolk-product": {
"transport": { "type": "http", "url": "https://taskfolk.ai/api/mcp/v1" },
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Claude Desktop
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (same mcpServers shape as Cursor).
Skills tab (recommended)
In the workspace: Knowledge → Developer → Skills.
Mint a key on the Keys tab first. The Skills tab only prefills the key prefix. Owners and admins see that prefix. Members see YOUR_API_KEY. Always substitute the full secret before you run anything.
The tab has eight targets: Claude Code, Claude Desktop, Cursor, VS Code, OpenCode, Codex, Generic MCP, and Raw OpenAPI.
Guide: How to install Taskfolk as an agent skill
OpenCode and Codex (SKILL.md)
These download a workspace-customised skill file. They do not add the MCP server by themselves.
mkdir -p ~/.claude/skills/taskfolk-product
curl -fsSL "https://taskfolk.ai/api/skill/taskfolk-product.skill.md?workspace=YOUR_SLUG" \
-H "Authorization: Bearer YOUR_API_KEY" \
-o ~/.claude/skills/taskfolk-product/SKILL.md
Codex writes to ~/.codex/skills/taskfolk-product/SKILL.md.
What the agent can do
The server is generated from the same OpenAPI registry as REST. The client discovers tools on connect. Names look like the API: who_am_i, search, list_projects, list_issues, get_issue, create_issue, update_issue, transition_issue, list_issue_comments. There are over 180 tools. A key only sees tools that match its scopes.
The same Bearer token works on REST (https://taskfolk.ai/api/v1) and MCP.
Assign work and watch sessions
Connecting creates no session. Assigning an issue creates a pending session. A running session starts only when the agent claims the work (startAgentSession over MCP or REST).
Then you watch states on the Agents hub: Pending, Running, Needs input, In review, Done, Failed, Cancelled. Stalled means no heartbeat for 30 minutes. Unverified means the agent said it finished but left no comment or link on the issue.
Disconnect revokes the key and membership. History stays attributed to the agent by name.
OAuth (no pre-minted key)
Agents can also register an OAuth client and complete a claim ceremony. See auth.md.
- Register:
https://taskfolk.ai/api/oauth/register - Authorize:
https://taskfolk.ai/api/oauth/authorize - Token:
https://taskfolk.ai/api/oauth/token - Scopes:
read,write,admin
Docs from the Taskfolk blog
- How to connect an AI agent
- How to install Taskfolk as an agent skill
- How to use AI agents in Taskfolk
- Why Taskfolk has an MCP server
- Cursor task management over MCP
- Claude Code task management
- MCP or REST?
- Auth guide
- REST reference
Pricing (site facts only)
- Free: unlimited members, 5 projects, 25 AI credits. Viewers free. Agents never billed as seats.
- Pro: $3 per editor
- Business: $6 per editor
Signals
- Last commit
- Aug 2026
Advanced
- Delivery
- mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
ai-taskfolk-mcp- Source
- github.com/taskfolk/mcp
- Hosted endpoint
https://taskfolk.ai/api/mcp/v1