MCP Integration

AgentTasks is a native Model Context Protocol (MCP) server. Any MCP-compatible AI client — Claude Desktop, Cursor, Windsurf, and more — can connect directly to your team's tasks without writing any code.

Quick Setup (3 steps)

Step 1: Create an MCP Token

In your team, go to Integrations in the sidebar. Click New Token, give it a name (e.g. "Claude Desktop"), and copy the token. It's shown only once.

Step 2: Add to your AI client

Paste the config snippet into your client's MCP settings file.

Claude Desktop — file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

json

{
  "mcpServers": {
    "agenttasks": {
      "type": "http",
      "url": "https://app.agenttasks.net/api/mcp",
      "headers": {
        "Authorization": "Bearer at_mcp_YOUR_TOKEN_HERE"
      }
    }
  }
}

Cursor — file: .cursor/mcp.json in your project root

json

{
  "mcpServers": {
    "agenttasks": {
      "url": "https://app.agenttasks.net/api/mcp",
      "headers": {
        "Authorization": "Bearer at_mcp_YOUR_TOKEN_HERE"
      }
    }
  }
}

`Step 3: Start using it`

In your AI conversation, just ask naturally — the AI will use AgentTasks tools automatically:

"Show me all pending tasks"
"Create a task: implement user auth, high priority"
"Mark task X as done"

`Available Tools`

The AgentTasks MCP server exposes 8 tools:

Tool	Description
`list_projects`	List all projects in your team. Call this first to get project IDs.
`list_tasks`	List tasks. Supports filtering by status, priority, and project.
`get_task`	Get full details of a single task by ID.
`create_task`	Create a new task with title, description, priority, and due date.
`update_task`	Update task fields (title, description, priority, due date).
`claim_task`	Claim a task — moves it to in_progress status.
`complete_task`	Mark a task as completed. Task must be in_progress first.
`move_task`	Move a task to any allowed status manually.

`MCP Server Details`

Endpoint	`https://app.agenttasks.net/api/mcp`
Protocol	MCP 2024-11-05, Streamable HTTP (JSON-RPC 2.0)
Auth	`Authorization: Bearer at_mcp_<token>`
Required header	`Accept: application/json, text/event-stream`

`FAQ`

`Can I create multiple tokens?`

Yes. Create one token per client (e.g. one for Claude Desktop, one for Cursor). You can revoke any token individually from the Integrations page without affecting others.

`Is the token scoped to a specific team?`

Yes. Each MCP token is bound to the team it was created in. It can only read and write tasks within that team.

`Can I use the MCP server directly via curl?`

Yes. Example — list all tools:

bash

curl -X POST https://app.agenttasks.net/api/mcp \
  -H "Authorization: Bearer at_mcp_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}'

`What status transitions are allowed?`

pending → in_progress, closed
in_progress → completed, pending, closed
completed → closed, in_progress
closed → (terminal, no further transitions)