mcpField
T
Taskfolk

Taskfolk

Remote
taskfolk.aiProductivity0Updated 10w ago

About Taskfolk

Taskfolk is a hosted project-management MCP server for teams that assign work to AI agents. Agents join as named workspace members and can work with live project boards through more than 180 scoped tools.

Key features

  1. 01Live project and issue access
  2. 02Create, update, and transition issues
  3. 03Claim assigned work and comment
  4. 04Track agent session states
  5. 05Bearer key or OAuth 2.0 authentication

Use cases

  1. 01Assign tickets to named AI agents
  2. 02Review agent progress in the Agents hub
  3. 03Let agents comment on and update issues

MCP support

Exposes Taskfolk project-management tools to MCP clients over Streamable HTTP. Access is controlled by API-key scopes or OAuth 2.0 scopes.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://taskfolk.ai/api/mcp/v1
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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.

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

  1. Open your workspace sidebar, then Agents.
  2. Click Connect agent. You need owner, admin, or member (the agent.connect permission). Viewers and guests cannot connect.
  3. Name the agent like a teammate seat, for example Omar's Claude Code.
  4. 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.
  5. 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.
  6. 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

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.