Workspace MCP

Prefer a hosted server (no install)? See Hosted Taskade MCP. It creates projects, edits tasks in existing projects (added August 2026), manages & prompts agents, and edits your Taskade Genesis app's source.

Not sure which Taskade MCP you need? See Which Taskade MCP do I want?.

Workspace MCP connects MCP-compatible AI tools to your Taskade workspace content.

Supported clients include Claude Desktop, Cursor, Claude Code, Windsurf, and VS Code.

The local server wraps REST API v1. It provides full task read and write access.

This is one of three MCP paths. See Which Taskade MCP do I want? before you choose.

What is MCP?

The Model Context Protocol lets AI assistants interact with external tools and data sources. The @taskade/mcp-server package exposes Taskade's API as MCP tools your AI client can call.

The MCP client talks to a locally run server, which wraps REST API v1 to reach your workspace content.

Install & run

The server is published as @taskade/mcp-server on npm. Run it on demand with npx.

You do not need a global installation:

npx -y @taskade/mcp-server

The server reads a Personal Access Token from TASKADE_API_KEY.

Create the token in Settings > API. This page also manages OAuth 2.0 clients and webhooks.

Configure Claude Desktop

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "taskade": {
      "command": "npx",
      "args": ["-y", "@taskade/mcp-server"],
      "env": {
        "TASKADE_API_KEY": "your_api_token_placeholder"
      }
    }
  }
}

Configure Cursor

Cursor uses the same configuration shape (in ~/.cursor/mcp.json or the project's .cursor/mcp.json):

{
  "mcpServers": {
    "taskade": {
      "command": "npx",
      "args": ["-y", "@taskade/mcp-server"],
      "env": {
        "TASKADE_API_KEY": "your_api_token_placeholder"
      }
    }
  }
}

HTTP / SSE mode

HTTP/SSE mode is available from source only: the npm-published CLI is stdio-only. Clone github.com/taskade/mcp and run the server package's HTTP entry.

When you run the HTTP source entry, the server listens on http://localhost:3000.

Set PORT to change the port. Connect over SSE at http://localhost:3000/sse?access_token=your_api_token_placeholder.

HTTP mode accepts the token as a query parameter (?access_token=…). Only use this on a trusted local network or behind TLS. Never expose it publicly.

Example Usage in Claude

After configuration, ask Claude to do tasks such as:

• "Spin up next week's client-onboarding tasks and assign them."
• "Mark every overdue invoice task complete and tell me what's left."
• "Create a project for the Q3 launch with a task per milestone."
• "Summarize what changed in my Marketing space this week."
• "List all my Taskade workspaces"
• "Create a task in my Sales Pipeline project to follow up with the client"
• "Show me the tasks in my Sales Pipeline project and mark the first one complete"
• "Add a due date of next Friday to task X"

Full tool reference

This section groups every exposed tool by category. Use it to configure exact tool calls.

The npm-published server (0.1.1) exposes 62 tools. The table below lists all 62 by name.

Seven categories hold 57 tools that mirror the REST API v1 operations this server wraps. An eighth category adds five API v2 (beta) tools, introduced in 0.1.0.

The API v2 (beta) layer covers agent prompts, agent chat, and webhook subscriptions.

It ships in v0.1.0 and later, and is on npm as of 0.1.1. The v2 webhook tools use the legacy subscription operations.

For signed webhooks, use the Webhook Registration API.

Plan Availability

Workspace MCP wraps the public REST API v1, so its tools inherit that API's gating rather than a separate MCP entitlement. Most v1 endpoints carry no plan gate.

One plan gate reaches this catalog. subscribeWebhook needs Pro or above, so Free and Starter are below the line. On a lower plan it returns 402 with code: "PAYMENT_REQUIRED". unsubscribeWebhook stays open on every plan, so a downgraded account can still remove its existing hooks.

Those two tools call the legacy unsigned subscription operations. The signed Webhook Registration API is a separate surface, and this server exposes no tool for it.

The paid mcp.access entitlement gates the Hosted Taskade MCP server, not this one.

If you receive a plan error, examine your subscription in account settings. Upgrade at taskade.com/pricing if necessary.

Resources