Log inSubmit server
Taskfolk logo

Taskfolk

Hosted project-management MCP server for connecting AI agents to Taskfolk workspaces.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Taskfolk

Pick your client, then add it in one click or paste the config.

SSE (Remote)
Server URL
https://taskfolk.ai/api/mcp/v1

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Taskfolk MCP server connects AI agents to a hosted Taskfolk workspace over Streamable HTTP. Agents join as named workspace members, discover scoped tools, and can read boards, manage issues, comment, and change statuses. Use it when an agent needs to participate in team project management with work attributed to a specific agent identity. Authentication supports bearer API keys or OAuth 2.0 with PKCE.

Use cases

  • Review live project boards
  • Create and update issues
  • Claim assigned tickets
  • Comment on team work
  • Track agent session states

Key features

  • Hosted Streamable HTTP endpoint
  • Bearer API key authentication
  • OAuth 2.0 with PKCE
  • Scoped discovery of more than 180 tools
  • Issue, project, and comment management
  • Agent session tracking

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 41d

How Taskfolk works

What the Taskfolk MCP server does

The Taskfolk MCP server gives AI agents access to project-management work in a Taskfolk workspace. Each connected agent appears as a named workspace member, allowing people to see which agent performed an action. Agents can inspect live boards, claim assigned tickets, add comments, and move issues through their workflow.

The hosted endpoint is https://taskfolk.ai/api/mcp/v1. There is no local executable to install. The server is generated from the same OpenAPI registry as Taskfolk's REST API, so its tools follow the API's naming and resource structure.

How it works

A workspace administrator or another member with the agent.connect permission creates an agent from the Agents area, names it, and copies an API key. The key is shown in full only once. The agent then connects to the shared MCP endpoint using an Authorization bearer header.

The Taskfolk MCP server exposes tools dynamically when a client connects. A key only receives tools allowed by its scopes. Example tool names include who_am_i, search, list_projects, list_issues, get_issue, create_issue, update_issue, transition_issue, and list_issue_comments; the service provides more than 180 tools.

Assigning an issue creates a pending session, but a running session begins only after the agent claims the work through startAgentSession over MCP or REST. The Agents hub reports states such as Pending, Running, Needs input, In review, Done, Failed, and Cancelled. A missing heartbeat for 30 minutes marks a session stalled.

Setup and configuration

Configure the hosted URL in a client that supports MCP over HTTP and provide the full API key in the Authorization header. The README includes setup formats for Claude Code, Cursor, VS Code, and Claude Desktop. Workspace-specific skill files are also available for OpenCode and Codex, but downloading a skill file does not itself register the MCP server.

OAuth 2.0 with PKCE is available when a pre-created API key is not suitable. The OAuth endpoints support read, write, and admin scopes. The same bearer token can also authenticate against the Taskfolk REST API at https://taskfolk.ai/api/v1.

Tools and capabilities

The Taskfolk MCP server supports operations across Taskfolk's project-management API, subject to the connected key's scopes. Supported work includes:

  • Identifying the connected workspace member
  • Searching workspace data
  • Listing projects and issues
  • Reading individual issues and their comments
  • Creating and updating issues
  • Transitioning issue status
  • Claiming assigned work and starting agent sessions
  • Reporting activity that humans can review in the Agents hub

Agents are not counted as billed seats, and a workspace can have up to 25 live agents.

Limitations and notes

This is a hosted service, not a repository that provides a local server binary. Connecting an agent does not start a work session; assignment and claiming are separate steps. Disconnecting revokes the key and membership, although prior history remains attributed to the agent's name.

The workspace must have an available agent connection, and viewers and guests cannot connect agents. Taskfolk shows a newly created API key only once; losing it requires disconnecting and reconnecting the agent. A session can be marked unverified when an agent reports completion without leaving a comment or issue link.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Taskfolk

Taskfolk is an MCP server that connects AI agents to Taskfolk workspaces for project management. Its main tools let agents inspect projects and issues, search workspace data, create or update issues, add comments, transition status, and start assigned sessions. Agents authenticate with a bearer API key or OAuth 2.0 with PKCE.

Use the hosted endpoint rather than installing a local binary. Create an agent in the Taskfolk workspace, copy its API key, and configure your MCP client with `https://taskfolk.ai/api/mcp/v1` and an Authorization bearer header. The README provides client-specific examples for Claude Code, Cursor, VS Code, and Claude Desktop.

Yes, Taskfolk works with Cursor through its MCP configuration file. Add the hosted endpoint under `mcpServers` in `~/.cursor/mcp.json`, then set the Authorization header to `Bearer YOUR_API_KEY`. The full key must be used; the workspace displays it only once.

Yes, agents can create and update issues when their key has the required scopes. The available tools include `create_issue`, `update_issue`, `transition_issue`, and issue-reading and commenting operations. Tool visibility depends on the scopes assigned to the connected key.

Taskfolk starts a pending session when work is assigned, but the session becomes running only after the agent claims it through `startAgentSession`. The Agents hub then shows states including Running, Needs input, In review, Done, Failed, and Cancelled, along with stalled or unverified conditions.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTaskfolk AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/taskfolk-2?style=directory)](https://allmcps.com/mcp/taskfolk-2)
HTML Embed
<a href="https://allmcps.com/mcp/taskfolk-2"><img src="https://allmcps.com/api/badge/taskfolk-2?style=directory" alt="Taskfolk on AllMCPs" /></a>