Taskade MCP — Install & Live Demo

Name: Taskade MCP MCP Server
Author: taskade

Why use it

Key features

Read/write Taskade projects, tasks, comments
Run Taskade AI agents from inside Claude
OpenAPI→MCP scaffold: npx @taskade/mcp gen ./openapi.json
Workspace-scoped auth tokens
Streaming responses for long agent runs

Live Demo

What it looks like in practice

taskade-mcp.replay ▶ ready

0/0

Install

Pick your client

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

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

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

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

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

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

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "taskade-mcp",
      "command": "npx",
      "args": [
        "-y",
        "@taskade/mcp"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "taskade-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@taskade/mcp"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add taskade-mcp -- npx -y @taskade/mcp

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Taskade MCP

Turn meeting notes into a Taskade project with assigned tasks

👤 Project managers ⏱ ~15 min intermediate

When to use: You just finished a meeting and have notes in a file.

Prerequisites

Server/skill installed and authenticated — See repo README

Flow

Parse the notes

Read /workspace/notes/2026-05-21-kickoff.md and extract action items as 'assignee — action — due'.✓ Copied

→ Structured list of action items
Push to Taskade

Create a Taskade project 'Q3 Kickoff' in workspace X and add each action item as a task with the right assignee and due date.✓ Copied

→ Project URL + per-task confirmations

Outcome: A fully populated Taskade project from raw notes in one shot.

Pitfalls

Workspace ids and assignee emails must match Taskade exactly — Workspace ids and assignee emails must match Taskade exactly — fetch them first with list_projects/list_members.

Combine with: filesystem · gmail

Combinations

Pair with other MCPs for X10 leverage

taskade-mcp + filesystem

Pair with filesystem for complementary capabilities

Use this server together with filesystem to complete a multi-step task.✓ Copied

taskade-mcp + gmail

Pair with gmail for complementary capabilities

Use this server together with gmail to complete a multi-step task.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_projects	workspace_id	Find a project to work on	1 API call
create_task	project_id, title, due	Add a new task	1 API call
run_agent	agent_id, input	Invoke a Taskade-side AI agent	Taskade AI credits

Cost & Limits

What this costs to run

API quota: See provider docs for rate limits
Tokens per call: Varies by tool
Monetary: See repo README for pricing details
Tip: Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets

Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

401 Unauthorized

Generate a personal access token at taskade.com/settings/personal-access-tokens and set TASKADE_API_KEY.

Verify: list_projects returns at least one project

agent_id not found

Agents are workspace-scoped. Use list_agents in the right workspace first.

Verify: list_agents returns the agent you want

Alternatives

Taskade MCP vs others

Alternative	When to use it instead	Tradeoff
Linear MCP	Engineering-focused issue tracking	Less general; better for code teams

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills