Taskade MCP Server – OpenAPI to AI Agent Tools

TL;DR

TL;DR: The official Taskade MCP server converts any OpenAPI 3.x spec into 62 ready-to-use MCP tools, letting Claude, Cursor, or any MCP client interact with Taskade’s full API — or any other API you define.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: taskade.com ← verified
• Source repository: github.com/taskade/mcp ← README read end-to-end
• License: MIT ← verified via GitHub API license.spdx_id
• HN launch thread: news.ycombinator.com/item?id=44183166

What Is Taskade MCP?

Taskade MCP is an official Model Context Protocol server from Taskade. It ships in two parts:

1. MCP Server — connects Taskade workspaces to any MCP-compatible AI client (Claude Desktop, Cursor, Windsurf, VS Code)
2. OpenAPI Codegen — generates MCP tools from any OpenAPI 3.x spec, not just Taskade’s own API

The repo describes it as:

“Connect Taskade to Claude Desktop, Cursor, Windsurf, or any MCP client.”

It offers 62 built-in tools covering workspaces, projects, tasks, AI agents, agent chat, webhooks, knowledge bases, templates, media, and sharing. The OpenAPI codegen lets you extend this pattern to any REST API.

Setup Workflow

Step 1: Install the MCP Server

npx -y @taskade/mcp-server

Step 2: Get Your Taskade API Key

Generate a Personal Access Token at taskade.com/settings/api.

Step 3: Configure Claude Desktop

Add to your claude_desktop_config.json:

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

Step 4: Zero-Install Remote Option (No Local Setup)

If you prefer not to install anything locally, add Taskade as a remote MCP server directly in Claude Web or Claude Desktop:

https://www.taskade.com/mcp

This uses OAuth — authorize once and it works across sessions without a local install or API key copy-paste. Currently works with Claude (web, Desktop, mobile) and Claude Code; more clients are rolling out.

Step 5: Use OpenAPI Codegen for Custom APIs

npm install --dev @taskade/mcp-openapi-codegen @readme/openapi-parser

Point the codegen at any OpenAPI 3.x file to auto-generate MCP tool definitions. The README includes a complete flow for turning any OpenAPI spec into a working MCP toolset.

Deeper Analysis

What the 62 Tools Cover

The built-in tools span:

• Workspaces — create, list, manage workspace-level settings
• Projects — CRUD operations on projects within workspaces
• Tasks — create, update, complete, delete tasks with full attribute support
• AI Agents — create and manage Taskade’s built-in AI agents
• Agent Chat — programmatic chat interactions with agents
• Webhooks — subscribe to workspace events
• Knowledge Bases — manage Taskade knowledge bases
• Templates — access and instantiate project templates
• Media — upload and manage files and attachments
• Sharing — control sharing permissions across collaborators

OpenAPI Codegen Use Cases

The codegen transforms any OpenAPI 3.x spec into MCP tool JSON. This means:

• You can wrap your company’s internal API as MCP tools and connect it to Claude
• You can use third-party APIs (Stripe, Linear, Notion) that have OpenAPI specs
• The generated tools are immediately usable in any MCP-compatible client

Cursor and VS Code Support

The README includes step-by-step configuration for both Cursor and VS Code MCP integrations, not just Claude Desktop. The Cursor setup uses the cursor://anysphere.cursor-deeplink/mcp/install deep link for one-click installation.

Practical Evaluation Checklist

• [x] README read end-to-end — all commands verified
• [x] GitHub metadata verified (151 stars, MIT license)
• [x] npm package exists and matches (@taskade/mcp-server)
• [x] OpenAPI codegen package verified (@taskade/mcp-openapi-codegen)
• [x] Remote MCP server option confirmed (zero-install, OAuth-based)
• [x] Multi-client support confirmed (Claude, Cursor, Windsurf, VS Code)

Security Notes

• API key required for self-hosted MCP server — never commit it to source control
• OAuth remote option avoids key sharing — authorize through Taskade’s OAuth flow instead
• Server-side remote MCP (taskade.com/mcp) means your API key stays on Taskade’s servers; only the OAuth token lives client-side

FAQ

Q: Does this work with Windsurf or other MCP clients besides Claude? A: Yes. The README explicitly mentions Cursor, Windsurf, and VS Code in addition to Claude Desktop. Any MCP-compatible client should work.

Q: How does the zero-install remote MCP option work? A: Adding https://www.taskade.com/mcp as a remote server uses Taskade’s OAuth flow to authenticate. The MCP handshake happens entirely through Taskade’s hosted endpoint, so no local npx install or API key is needed on your machine.

Q: Can I generate MCP tools from a custom API, not just Taskade’s? A: Yes. The @taskade/mcp-openapi-codegen package takes any OpenAPI 3.x spec and produces MCP tool definitions. You are not limited to Taskade’s own API.

Q: What is the OpenAPI codegen dependency? A: The codegen requires both @taskade/mcp-openapi-codegen and @readme/openapi-parser as peer dependencies.

Conclusion

Taskade MCP bridges the gap between REST APIs and AI agents. The official MCP server gives Claude, Cursor, and other clients direct access to Taskade’s full productivity suite via 62 built-in tools. The OpenAPI codegen extends this further — any documented API can become a set of MCP tools your AI assistant can call.

If you already use Taskade or need to connect an AI agent to a REST API, this is a zero-infrastructure way to do it. The hosted remote MCP option removes even the local install step.

Repo: github.com/taskade/mcp — 151 stars, MIT licensed.