Skip to main content
mcpSource-backedReview first Safety Privacy

Taskade MCP Server for Claude

Connect Claude to Taskade — manage workspaces, projects, tasks, and AI agents — with the official Taskade MCP server, covering 57 tools for the full Taskade platform including projects, tasks, AI agent conversations, media, and templates.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • Tools can create, update, and delete projects, tasks, and AI agents in your Taskade account — changes affect live data.
  • AI agent tools (`agentCreate`, `agentUpdate`, `agentDelete`) modify live agent configurations — review before executing.

Privacy notes

  • Workspace names, project content, task details, and AI agent conversation history from your Taskade account are surfaced in Claude's context.
  • Your `TASKADE_API_KEY` grants full account access — keep it in the MCP config env and never commit it to version control.

Prerequisites

  • A Taskade account — log in at taskade.com.
  • A Taskade API key: Settings → Apps & Integrations → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "taskade": {
      "command": "npx",
      "args": ["-y", "@taskade/mcp-server"],
      "env": {
        "TASKADE_API_KEY": "<your-api-key>"
      }
    }
  }
}

About this resource

Overview

The Taskade MCP Server is the official Model Context Protocol server from Taskade, providing 57 tools for the full Taskade platform: workspaces, folders, projects, tasks, AI agents, media, and templates. It lets Claude read and write your Taskade data in natural language — create projects from templates, manage tasks, inspect agent conversations, and more. Licensed under MIT.

Key capabilities

  • Workspaces & folders — list all workspaces, navigate folder hierarchies.
  • Projects — create, copy, get, and manage projects within workspaces.
  • Tasks — create, update, delete, complete, and uncomplete tasks.
  • AI agents — create, update, delete agents; browse conversation history.
  • Templates — instantiate projects from Taskade's template library.
  • Media — list, get, and delete media attachments.

Tools (57 total, key selection)

Tool Category Purpose
workspacesGet Workspaces List all workspaces
workspaceFoldersGet Folders List folders in a workspace
workspaceCreateProject Projects Create a project in a workspace
projectGet / projectCreate / projectCopy Projects Project CRUD
taskCreate / taskUpdate / taskDelete Tasks Task lifecycle
taskComplete / taskUncomplete Tasks Toggle task completion
agentCreate / agentUpdate / agentDelete AI Agents Agent management
agentConvosGet / agentConvoGet AI Agents Agent conversation history
projectFromTemplate Templates Instantiate project from template
mediasGet / mediaGet / mediaDelete Media Media management

How it compares

MCP server Tasks AI agents Templates Projects Notes
Taskade MCP Yes Yes Yes Yes 57 tools, official
Asana MCP Yes No Limited Yes Asana-only
Linear MCP Yes (issues) No No Yes (teams) Engineering focus
Notion MCP Partial No Yes Yes (pages/DBs) Document-first

Taskade is unique in combining task management with built-in AI agent creation and conversation history in a single MCP integration.

Installation

Claude Code

claude mcp add taskade \
  -e TASKADE_API_KEY=<your-api-key> \
  -- npx -y @taskade/mcp-server

Claude Desktop

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

Generate your API key at Settings → Apps & Integrations → API → Generate API Key in your Taskade account.

Requirements

  • A Taskade account with an API key.
  • Node.js (for npx).
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Keep TASKADE_API_KEY in the MCP config env; never commit it to version control.
  • Task and agent operations modify live data — review Claude's planned actions before confirming.

Source Verification Notes

Verified on 2026-06-18:

  • Official MCP repository taskade/mcp (MIT) documents the @taskade/mcp-server npm package, TASKADE_API_KEY environment variable, all 57 tools across workspaces, folders, projects, tasks, AI agents, templates, and media, and the Claude Code install command.
  • Taskade's learn page at taskade.com/learn/connect/mcp-server describes the integration setup.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector pattern used above.

Source citations

Add this badge to your README

Show that Taskade MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/taskade-mcp-server.svg)](https://heyclau.de/entry/mcp/taskade-mcp-server)

How it compares

Taskade MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldTaskade MCP Server for Claude

Connect Claude to Taskade — manage workspaces, projects, tasks, and AI agents — with the official Taskade MCP server, covering 57 tools for the full Taskade platform including projects, tasks, AI agent conversations, media, and templates.

Open dossier
Trello MCP Server

MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude.

Open dossier
Backlog MCP Server for Claude

Manage Backlog projects from Claude — create and update issues, comment on tickets, manage wiki pages, review pull requests, and navigate your Nulab Backlog space — with the official Backlog MCP server supporting stdio and HTTP transports.

Open dossier
Todoist MCP Server

MCP server for Todoist task and project management, with tools for tasks, subtasks, projects, sections, labels, comments, reminders, filters, activity, backups, collaboration, bulk operations, and dry-run testing.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorTaskadeJarad DeLorenzoNulabgreirson
Added2026-06-182026-06-062026-06-182026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesTools can create, update, and delete projects, tasks, and AI agents in your Taskade account — changes affect live data. AI agent tools (`agentCreate`, `agentUpdate`, `agentDelete`) modify live agent configurations — review before executing.Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools. Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows. File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files. Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards. Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.Tools can create, update, and delete projects, issues, wikis, and pull requests — changes affect your live Backlog space. Use `ENABLE_TOOLSETS` to restrict which tool groups are available if you only need read access.Todoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state. Bulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once. Dry-run mode simulates mutation operations but still queries real Todoist data for validation. Pro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data. Require confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
Privacy notesWorkspace names, project content, task details, and AI agent conversation history from your Taskade account are surfaced in Claude's context. Your `TASKADE_API_KEY` grants full account access — keep it in the MCP config env and never commit it to version control.Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client. Active board and workspace selections may persist locally in Trello MCP configuration. Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data. Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts. Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.Issue content, comments, wiki pages, pull request details, and user information from your Backlog space are surfaced in Claude's context. Your `BACKLOG_API_KEY` grants account-level Backlog access — keep it in the MCP config env and never commit it to version control.Todoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client. Task names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data. Bulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request. Backup download tools can expose a broad historical snapshot of Todoist data. Keep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
Prerequisites
  • A Taskade account — log in at taskade.com.
  • A Taskade API key: Settings → Apps & Integrations → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Trello API key and token with access to the boards and workspaces Claude may use.
  • Bun-compatible published package runtime or an MCP client that can launch the packaged stdio server through npx.
  • Optional `TRELLO_BOARD_ID` or `TRELLO_WORKSPACE_ID` when a default board or workspace should be selected at startup.
  • Optional `TRELLO_ALLOWED_WORKSPACES` to constrain the token to specific approved Trello workspaces.
  • A Backlog account on backlog.com or your Backlog.jp/enterprise space.
  • A Backlog API key: Personal Settings → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Todoist API token from Todoist integrations developer settings.
  • Node.js 18 or newer for the npm stdio server.
  • Review of whether the token has access to personal, shared, Pro, Business, or workspace features.
  • Optional `DRYRUN=true` for simulating mutation tools while still validating against real Todoist data.
Install
claude mcp add taskade -e TASKADE_API_KEY=<your-api-key> -- npx -y @taskade/mcp-server
npx @delorenj/mcp-server-trello
claude mcp add backlog -e BACKLOG_DOMAIN=yourspace.backlog.com -e BACKLOG_API_KEY=<your-api-key> -- npx backlog-mcp-server
npx @greirson/mcp-todoist
Config
{
  "mcpServers": {
    "taskade": {
      "command": "npx",
      "args": ["-y", "@taskade/mcp-server"],
      "env": {
        "TASKADE_API_KEY": "<your-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "trello": {
      "command": "npx",
      "args": [
        "@delorenj/mcp-server-trello"
      ],
      "env": {
        "TRELLO_API_KEY": "your-api-key",
        "TRELLO_TOKEN": "your-token",
        "TRELLO_ALLOWED_WORKSPACES": "workspace-id-1,workspace-id-2"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "backlog": {
      "command": "npx",
      "args": ["backlog-mcp-server"],
      "env": {
        "BACKLOG_DOMAIN": "yourspace.backlog.com",
        "BACKLOG_API_KEY": "<your-api-key>",
        "MAX_TOKENS": "50000"
      }
    }
  }
}
{
  "mcpServers": {
    "todoist": {
      "command": "npx",
      "args": [
        "@greirson/mcp-todoist"
      ],
      "env": {
        "TODOIST_API_TOKEN": "your-api-token",
        "DRYRUN": "true",
        "TODOIST_UNIFIED_TOOLS": "true"
      },
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.