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-servernpm 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:
| Option | How It Works | Best For |
|---|---|---|
| Hosted MCP Server (Beta) | Connects directly to Taskade via OAuth 2.0. No API key needed. | Claude Desktop, Cursor, and clients that support OAuth-based MCP |
Open-Source MCP Server (@taskade/mcp-server) |
Runs locally via npx with a Personal Access Token | n8n, custom clients, HTTP/SSE setups |