Taskade MCP Server

Overview

The Taskade MCP server connects your Taskade workspace to any MCP-compatible AI tool. Claude Desktop. Cursor. Windsurf. VS Code. Any client that speaks MCP. Once connected, your AI assistant can read your projects, agents, and automations, create projects and agents, edit the tasks inside an existing project, and edit your Taskade Genesis app.

TL;DR: Connect Taskade to Claude Desktop, Cursor, or VS Code and your AI assistant works with your real workspace. It can read your projects, turn notes into a new project, create and update tasks in a project you already have, build and question your AI agents, and edit your Taskade Genesis app. One-click sign-in, included on every paid plan. See Pricing for plan details.

  ┌──────────────────┐    MCP     ┌──────────────────┐
  │ Claude Desktop   │ ─────────▶ │ Taskade Workspace│
  │ Cursor / Windsurf│  OAuth or  │ projects, agents │
  │ VS Code / n8n    │  API token │ automations, app │
  └──────────────────┘            └──────────────────┘
         ▲                                  │
         └──────── tool calls ──────────────┘

🔬 Beta: The hosted Taskade MCP server (v6.148.0+) is in beta. You can also use the open-source @taskade/mcp-server npm package for a self-hosted option with 50+ tools.

💡 Note: Wondering whether Taskade can call out to an external MCP server? It can, through automations. The MCP Client connector points an automation at any remote MCP server and calls its tools as steps. An agent cannot reach a server on its own, so let it hand the work to an automation. Full picture: Taskade Agents and External MCP Servers and MCP Connectors.

Two Ways to Connect

Taskade offers two MCP server options:

Hosted MCP Server (Beta)

The hosted MCP server gives your AI tools direct access to your workspace. Your assistant sees five areas:

Plan Requirements

The hosted MCP server is available on every paid plan. The Free plan does not include hosted MCP access. You can still use the open-source @taskade/mcp-server package on any plan. See Pricing for the full plan matrix.

Why two tiers? The hosted server runs on Taskade infrastructure with OAuth sign-in and team-aware access. The open-source server runs on your machine with a Personal Access Token. Both expose the same workspace. Pick the hosted server when you want zero setup and team admin controls. Pick the open-source server when you need full local control or a custom HTTP endpoint.

Authentication

The hosted server uses OAuth 2.0 with PKCE. Fully standards-compliant. When you connect from Claude Desktop, Cursor, or another MCP client, Taskade opens a browser window for you to authorize access, with no manual API key setup. The access token carries the mcp scope.

A personal access token also works on the hosted endpoint, which is useful for a script or a client that cannot complete a browser sign-in. Create one in your settings and pass it instead of running the OAuth flow. Browser sign-in stays the recommended path for everyday use because it needs no key handling on your side.

Connect from Claude Desktop

Add this to your Claude Desktop config file (claude_desktop_config.json):

{
  "mcpServers": {
    "taskade": {
      "type": "http",
      "url": "https://www.taskade.com/mcp"
    }
  }
}

Restart Claude Desktop. It will open a browser window to authorize Taskade. Once approved, your workspace tools appear in the tools menu.

Connect from Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "taskade": {
      "type": "http",
      "url": "https://www.taskade.com/mcp"
    }
  }
}

Connect from Any MCP Client

Any client that supports the MCP protocol with OAuth 2.0 can connect to the hosted server at:

https://www.taskade.com/mcp

The server publishes OAuth metadata at the standard well-known endpoints for automatic discovery.

What Your AI Assistant Can Do

Once connected, your assistant works with your real Taskade workspace. Ask in plain language and it acts.

Find and read your work

• "What's on the Q2 roadmap?" Your assistant reads the project, tasks, owners, and due dates.
• "Check the Q2 roadmap and the launch plan for anything about the Henderson account." Name the projects and your assistant reads them.
• "Summarize what my research agent concluded yesterday." It reads the agent's past chats.
• "What automations are running in this workspace?" It lists them.

Create and update

• "Turn these meeting notes into a project." A real project appears in your workspace, structured into tasks.
• "Add the three follow-ups to the Q2 roadmap and give them Friday due dates." Since August 2026 your assistant can create, update, complete, move, and delete tasks in a project you already have, including due dates, notes, assignees, and custom field values.
• "Build me an agent that screens inbound service requests." The agent is created and ready to use.
• "Give that agent our service handbook as background." The project becomes the agent's knowledge.
• "Ask my analyst agent what the top three risks are." You get its answer without leaving your editor.

Edit your Taskade Genesis app

• "Add a status filter to the dashboard." Your assistant edits the app's code directly.

Task edits land in an existing project, so name the project you mean. Editing app code needs Collaborator access or above. Ask your assistant to read a file before it changes one, so an edit is never applied to a stale copy.

Everything respects your permissions. Your assistant sees only what your Taskade account can see.

Open-Source MCP Server

The open-source @taskade/mcp-server npm package provides 50+ tools across 7 categories. It runs locally on your machine and connects to Taskade via a Personal Access Token.

Prerequisites

• Node.js 18+ installed
• A Taskade Personal Access Token. Generate one at Settings → API

Quick Start

Run the MCP server with npx (no install needed):

npx -y @taskade/mcp-server

Or install globally:

npm install -g @taskade/mcp-server

Connect to Claude Desktop

Add this to your Claude Desktop config file (claude_desktop_config.json):

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

Restart Claude Desktop. You should see Taskade tools available in the tools menu.

Connect to Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

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

Connect via HTTP/SSE

For HTTP-based MCP clients, start the server in HTTP mode:

TASKADE_API_KEY=your-api-key npx @taskade/mcp-server --http

The server starts on localhost:3000. Connect your client to the SSE endpoint:

http://localhost:3000/sse?access_token=your-api-key

Available Tools (Open-Source)

The open-source MCP server exposes 50+ tools organized into 7 categories:

Workspaces

Projects

Tasks

AI Agents

Templates, Media & Personal

Use Cases

OpenAPI Codegen

The Taskade MCP monorepo also includes @taskade/mcp-openapi-codegen, a tool that generates MCP-compatible tools from any OpenAPI 3.0+ specification. This lets you create MCP servers for your own APIs.

npx @taskade/mcp-openapi-codegen --spec https://api.example.com/openapi.json

Frequently Asked Questions

Where do I get my API key?

Go to Settings → API and create a Personal Access Token. This is only needed for the open-source MCP server. The hosted server uses OAuth 2.0 instead.

Which plans include the hosted MCP server?

Every paid plan. The open-source @taskade/mcp-server npm package works on any plan with a Personal Access Token. See Pricing for the current plan matrix.

Which AI tools support MCP?

Claude Desktop, Cursor, Windsurf, VS Code (with MCP extension), n8n, and any tool that supports the Model Context Protocol.

Can I edit my Taskade Genesis app code via MCP?

Yes. The hosted MCP server's write_file tool lets you create, edit, and patch files in the app/ directory. You need Collaborator, Maintainer, or Owner role in the workspace.

Can I use this with AI agents inside Taskade?

This server is for connecting external AI tools into Taskade. For the opposite direction, use the MCP Client connector in an automation, which calls tools on any remote MCP server. Your agents work with their large built-in toolkit and your own custom tools, and they reach anything else by handing the work to an automation. See MCP Connectors for how the two directions differ.

Related guides

• MCP Connectors (Taskade Genesis). How the two MCP directions differ, and what to use today
• Automations. Connect Taskade to 100+ services from inside your workspace
• Developer API · Public API. Other programmatic entry points
• Tools for AI Agents. The built-in tools every agent can call today
• Custom AI Agents. Build agents with their own instructions, knowledge, and custom tools, and choose which tools each one can reach
• MCP Developer Docs. Setup for Claude, Cursor, and other clients. See advanced usage for multiple clients, troubleshooting, and security
• GitHub: taskade/mcp