Taskade MCP Server

Overview

The Taskade MCP server connects your Taskade workspace to Claude Desktop, Cursor, Windsurf, VS Code, and other AI tools. MCP stands for Model Context Protocol. It is the shared standard those tools use to reach your data, and any tool that speaks it is an MCP client. Once connected, your AI assistant can work with projects, tasks, agents, folders, templates, media, and your Taskade Genesis app.

TL;DR: Open Settings → API, choose Connect Cursor or Connect Claude, and replace the copied configuration's token placeholder. Paste it into your client to work with projects, tasks, agents, folders, templates, media, and Taskade Genesis apps. The hosted connection is available on every paid plan. See Pricing for details.

Connect the hosted MCP server

The hosted inbound server is https://www.taskade.com/mcp. It is on every paid plan. It is not limited to app files. A connected client can work with workspaces, projects, tasks, and agents, and it can inspect a Taskade Genesis app. The write_file tool writes only under app/.

Step 1: Create a token

Open Settings → API in Taskade. Create or copy a Personal Access Token.

Step 2: Copy the hosted configuration

Select Connect Cursor or Connect Claude.

Step 3: Add your token

Replace <paste-your-token-here> with your token.

Step 4: Open the client configuration

Open claude_desktop_config.json in Claude Desktop or .cursor/mcp.json in Cursor.

Step 5: Save the configuration

Paste the copied taskade server entry. Save the file.

Step 6: Restart the client

Restart the client. Workspace tools then appear in its tools menu. Treat the configuration as a secret because it now contains your token.

On Free, skip the hosted URL. Run the open-source taskade/mcp server on your own computer instead, with a Personal Access Token from Settings → API. Your AI tool starts that server and talks to it directly, a setup developers call stdio. Outbound MCP through an automation is a different path. See MCP Connectors.

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

🔬 Still evolving: The hosted Taskade MCP server (v6.148.0+) is available on every paid plan. Its tool set is still growing, so tools and behavior can change between releases. You can also run the open-source taskade/mcp server on your own computer with a Personal Access Token.

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

The hosted MCP server gives your AI tools direct access to your workspace. Your assistant can use these 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 browser sign-in and team-aware access. The open-source server runs on your machine with a Personal Access Token and exposes the public API surface. Use the hosted server for the broadest workspace and app access. Use the open-source server when you want to run it yourself, or when you need it reachable at a web address you control.

Authentication

The hosted server accepts two credentials, and either one works on its own.

Browser sign-in. Connect from Claude Desktop, Cursor, or another MCP client and Taskade opens a browser window for you to approve access. The access token it issues is limited to MCP access, so it cannot be used for anything else. Nothing is stored in your client configuration.

Personal Access Token. Create a token in Settings → API and paste it into your client configuration instead of running the browser flow. Use a token when your client cannot open a browser, or when you want one credential you manage and revoke yourself. Treat that configuration file as a secret.

Both paths sign you in as you. Your workspace role and your plan still decide what the client can reach.

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 speaks the MCP protocol can connect to the hosted server at:

https://www.taskade.com/mcp

The server advertises its sign-in details at the standard address clients look for, so a client that supports browser sign-in finds them on its own. A client that does not can send a Personal Access Token in the Authorization header instead, in the usual Bearer <token> form.

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 is 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. This includes 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 runs on your own computer. Your AI tool starts it and talks to it directly, with no web address in between. It connects to Taskade with a Personal Access Token. Use this path on any plan, including Free.

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. Check that Taskade tools appear 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

Some clients connect over a web address rather than starting the server themselves. For those, start the server in HTTP mode:

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

The server starts on localhost:3000. Point your client at the streaming address below. SSE is short for Server-Sent Events, the way the server pushes results back as they arrive.

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

Available Tools (Open-Source)

The open-source MCP server exposes workspace, project, task, agent, template, and media tools:

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

Can I connect Claude without creating a new Taskade account?

If you already have a Taskade account, point Claude Desktop at https://www.taskade.com/mcp and approve access. You do not create a second Taskade login. The client uses the same workspace. The taskade/mcp server on your own computer uses a token from Settings → API. The protocol itself is documented at modelcontextprotocol.io.

How do I use hosted MCP on a Free plan?

You cannot use the hosted inbound URL on Free. Hosted MCP at https://www.taskade.com/mcp is on every paid plan. On Free, run the taskade/mcp server on your own computer with a Personal Access Token. Outbound MCP through an automation still works on Free. Agent outbound MCP is off in production.

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 only. You need edit access in the workspace. Hosted MCP also reads projects, tasks, agents, and automations. It is not an app-files-only connection.

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 built-in tools 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