TL;DR: Build on Taskade with two HTTP APIs, MCP servers, and a TypeScript SDK. Use REST API v1 for full task CRUD and Action API v2 for prompting agents and bundles, authenticated by a personal access token or OAuth 2.0. Run
@taskade/mcp-serverto give Claude Desktop or Cursor access to your workspace, and use automations for webhooks and events.
Build on Taskade
This is your starting point for building on Taskade programmatically. Taskade exposes two HTTP APIs, MCP servers in both directions, 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 |
- 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? Reach for v1 when you need to write tasks or task metadata. Reach for v2 for agent prompting, agent lifecycle, and bundles. (v2 tasks are read-only.)
Authentication
- Personal Access Token: create at Settings → API (prefixed
tskdp_, up to 5, verified email). Send asAuthorization: Bearer tskdp_…. - OAuth 2.0: Authorization Code + PKCE for apps acting on behalf of other users. Endpoints:
/oauth2/authorize,/oauth2/token,/oauth2/register.
See the Public API Reference → Authentication.
MCP (Model Context Protocol)
Taskade speaks MCP in both directions:
| Direction | What it is | Guide |
|---|---|---|
| Inbound (local) | Run @taskade/mcp-server so Claude Desktop, Cursor, or Claude Code can use your workspace |
Taskade MCP Server → |
| Inbound (hosted) | The remote https://www.taskade.com/mcp server (OAuth) for editing Genesis app source |
Taskade MCP Server → Hosted |
| Outbound | Give your Taskade agents tools from external MCP servers and 31+ connectors | MCP Connectors → · Connect to External MCP → |
Run the inbound 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 (e.g. task completed) plus an HTTP Request action. To send data into Taskade, use the inbound Webhook trigger.