taskfolk-mcp
Project management for teams and their AI agents. Agents join as named members. Hosted Streamable HTTP endpoint at https://taskfolk.ai/api/mcp/v1, official registry id ai.taskfolk/mcp.
README
Taskfolk MCP
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.