Taskade MCP logo

Taskade MCP

by taskade

Manage Taskade workspaces, projects, tasks, agents, and related workflows from MCP-compatible AI clients.

Install Taskade MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-162": {
      "command": "npx",
      "args": [
        "-y",
        "@taskade/mcp-server"
      ],
      "env": {
        "TASKADE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 62 tools correctly (Today).

Overview

The taskade/mcp MCP server connects AI assistants to Taskade through hosted Streamable HTTP or a local stdio package. It exposes tools for browsing and changing workspaces, folders, projects, tasks, assignments, dates, notes, and project sharing, with additional hosted support for agents and conversations. OAuth 2.0 with PKCE is available on the hosted endpoint, while clients without OAuth can send a Taskade personal access token. Reach for it when an assistant needs to read or update Taskade work rather than only generate text.

Use cases

  • List workspaces and group open tasks by assignee
  • Create projects with tasks and due dates
  • Update task assignments, notes, and completion state
  • Build and query Taskade AI agents
  • Inspect or edit Genesis app source files

Key features

  • Workspace and folder discovery
  • Project creation and lifecycle management
  • Task editing, assignment, dates, and notes
  • AI agent and conversation operations
  • Hosted Streamable HTTP with OAuth
  • Local stdio package

Tools62

What Taskade MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 40d

What it can do

From the 62 tools this server returned when we ran it; 62 declare their own safety hints.

Can delete or modify data · 18Makes network requests · 3Read-only tools · 44
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age512 days
Maintainers4

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @taskade/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars169Stargazers on the source repository.
npm downloads525Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed62Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Taskade MCP works

What taskade/mcp MCP server does

The taskade/mcp MCP server gives compatible AI clients access to Taskade work-management data and actions. It can enumerate workspaces and folders, create or inspect projects, copy or complete projects, restore completed projects, and retrieve project members, custom fields, blocks, tasks, and share links. Task operations include creating, updating, moving, completing, deleting, assigning, and setting due dates or notes.

The repository contains both a hosted service and a local package. The hosted service includes a broader tool surface covering project and task operations, AI agents, conversations, and Genesis app source files. The local package is described as a stdio server and exposes 62 tools. The project is listed in the 🏢 Workplace & Productivity category because its primary use is managing structured work in Taskade through an AI assistant.

How it works

The hosted endpoint is https://www.taskade.com/mcp and uses Streamable HTTP. Clients that support the flow can authenticate with OAuth 2.0, PKCE, and dynamic client registration. The first unauthenticated initialization request returns a 401 so the client can begin sign-in. After authorization, the assistant can call read and write tools against the connected Taskade account.

Clients without OAuth support can send a Taskade personal access token in an HTTP Bearer header. Access still depends on the user’s Taskade account, workspace plan, and permissions. Tool calls may fail when the account lacks access to a workspace or project. Hosted tools also provide annotations that let clients distinguish read-only operations from changes such as deletion or replacement.

Setup and configuration

For the hosted taskade/mcp MCP server, configure the URL https://www.taskade.com/mcp in the client and complete Taskade sign-in. Claude supports adding it as a custom connector; Claude Code can add the endpoint with its HTTP transport. Cursor, VS Code, and Windsurf each provide documented MCP configuration paths in the repository instructions.

The repository also publishes @taskade/mcp-server as a local stdio option for clients that cannot connect to a remote server. Local operation requires a valid TASKADE_API_KEY, obtained from Taskade Settings > API. Clients that cannot perform OAuth can instead use the hosted endpoint with a personal access token in the Authorization header.

Tools and capabilities

The documented local tools cover:

  • Workspace and folder discovery, plus project creation and listing.
  • Project inspection, copying, completion, restoration, membership, fields, blocks, tasks, and share links.
  • Task creation, updates, deletion, movement, completion state, assignees, due dates, and notes.
  • Hosted AI-agent operations such as listing agents and conversations, creating or updating agents, managing knowledge projects or media, and prompting an agent.
  • Hosted Genesis app inspection and source-file writing through the relevant workspace tools.

Use read operations to gather project context before asking the assistant to make changes. Write operations can alter or remove Taskade data, so the client may request confirmation.

Limitations and notes

Hosted MCP access is included with paid Taskade plans beginning with Starter. On the Free plan, the workspace-listing operation returns no workspaces. The account’s role also limits which projects and workspaces can be changed.

OAuth failures may require reconnecting the client with the correct Taskade account. If a local server reports an invalid API key, create a new token in Taskade Settings > API.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Taskade MCP

taskade/mcp is an MCP server that connects AI assistants to Taskade and exposes tools for workspaces, folders, projects, tasks, agents, agent conversations, and webhooks. It supports hosted Streamable HTTP with OAuth or a local stdio package, allowing compatible clients to read and manage Taskade work through tool calls.

Use the hosted endpoint `https://www.taskade.com/mcp` without installing software, or use the repository’s `@taskade/mcp-server` local stdio package when your client cannot connect remotely. Hosted clients authenticate with OAuth; clients without OAuth can send a Taskade personal access token.

Yes, taskade/mcp works with Cursor through the hosted MCP URL. Add `https://www.taskade.com/mcp` to Cursor’s MCP configuration or use the repository’s Add to Cursor flow, then complete Taskade authentication.

It can list workspaces and folders, create and inspect projects, manage project state and sharing, and create, update, move, complete, delete, assign, and annotate tasks. The hosted tool set also includes AI-agent, conversation, and Genesis app operations.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTaskade MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-server-162?style=directory)](https://allmcps.com/mcp/mcp-server-162)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-server-162"><img src="https://allmcps.com/api/badge/mcp-server-162?style=directory" alt="Taskade MCP on AllMCPs" /></a>