TL;DR: Build on Taskade with two HTTP APIs, MCP servers, and a TypeScript SDK. REST API v1 covers full task CRUD plus project create, restore, copy, and sharing. Action API v2 handles prompting agents, bundles, and task writes, authenticated with a personal access token or OAuth 2.0. Run
@taskade/mcp-serverfor Claude Desktop or Cursor, and use automations for webhooks.
Build on Taskade
This is your starting point for building on Taskade programmatically. Taskade exposes two HTTP APIs, an MCP server your AI clients can connect to, and a TypeScript SDK (in preview).
APIs
Taskade ships two public APIs, both authenticated the same way (a personal access token or OAuth 2.0).
| API | Base URL | Style | Status | Best for |
|---|---|---|---|---|
| REST API v1 | https://www.taskade.com/api/v1 |
RESTful (GET/POST/PUT/DELETE) |
GA | Full task CRUD: assignees, dates, notes, custom fields |
| Action API v2 | https://www.taskade.com/api/v2 |
Action / RPC (POST /{operation}) |
Beta | Prompting agents, agent lifecycle, bundles, task writes in an existing project |
- Public API Reference →: every v1 endpoint, plus the v2 action operations
- Developer API Overview →: capabilities, auth, and the agent API
- Live specs: /api/documentation/v1 · /api/documentation/v2
v1 or v2? Both write tasks and task metadata since August 2026, and both can create, complete, restore, and copy a project. Reach for v2 for agent prompting, agent lifecycle, and bundles. Reach for v1 for single-task reads, which v2 does not have. Neither version can rename or delete a project, so do that in the app.
Authentication
- Personal Access Token: create at Settings → API (prefixed
tskdp_, up to 5, verified email). Send asAuthorization: Bearer tskdp_…. - OAuth 2.0: for apps acting on behalf of other users (Authorization Code flow). Endpoints:
/oauth2/authorize,/oauth2/token,/oauth2/register.
See the Public API Reference → Authentication.
MCP (Model Context Protocol)
Taskade acts as an MCP server. Your AI client connects in, and the hosted server is available on every paid plan:
| Option | What it is | Guide |
|---|---|---|
| Local | Run @taskade/mcp-server so Claude Desktop, Cursor, or Claude Code can use your workspace |
Taskade MCP Server → |
| Hosted | The remote https://www.taskade.com/mcp server (OAuth) for creating projects, editing tasks, managing agents, and editing Taskade Genesis app source |
Taskade MCP Server → Hosted |
The other direction runs through automations. The MCP Client connector calls tools on any remote MCP server as a step. An agent cannot reach a server on its own. Give agents outside data with the 100+ integrations, the built-in agent tools, or an automation they hand the work to.
Run the server with:
npx -y @taskade/mcp-server
(authenticated with TASKADE_API_KEY = your personal access token).
TypeScript SDK (Preview)
A generated TypeScript client (@taskade/sdk) is in preview and not yet on the public npm registry. Until it ships, call the API directly over HTTP (every endpoint is a plain HTTPS request). See the Public API Reference.
Webhooks & Events
There is no webhook-subscription endpoint. To receive Taskade events in your app, build an automation with a trigger (for example, task completed) plus an HTTP Request action. To send data into Taskade, use the inbound Webhook trigger.
Related guides
- Public API Reference. Every v1 endpoint and v2 action operation.
- Developer API Overview. Capabilities, auth, and the agent API.
- Taskade MCP Server. Give Claude Desktop, Cursor, or Claude Code your workspace.
- Integrations. 100+ bidirectional integrations for moving data in and out.
- Automations. Triggers and HTTP Request actions for your own endpoints.
- Developer Docs. The full reference: REST v1, Action API v2, guides, and MCP.