Overview
MCP lets an AI client access a workspace without a custom integration. Taskade provides two MCP servers.
Choose a server based on whether you need a local desktop connection or the hosted endpoint.
Choosing a server
| Workspace MCP | Hosted MCP | |
|---|---|---|
| Where it runs | Your machine, via npx |
Taskade infrastructure |
| Endpoint | local stdio | https://www.taskade.com/mcp |
| Transport | stdio | Streamable HTTP (no SSE) |
| Auth | Personal access token | Personal access token, or OAuth 2.0 with the mcp scope |
| Best for | Desktop AI clients you control | Remote clients, shared setups |
| Can edit Genesis app source | No | Yes |
Authentication
The hosted server implements the full OAuth discovery chain. A compliant client configures itself:
WWW-Authenticate: Bearer realm="mcp",
resource_metadata="https://www.taskade.com/mcp/.well-known/oauth-protected-resource"
An OAuth access token stays valid for 3600 seconds. A refresh rotates the pair and expires both tokens it replaces.
A personal access token also works. A personal token carries no OAuth scopes, so the server skips the scope check and authenticates you as the token's owner.
MCP is plan-gated per tool, not at the transport. Authentication succeeds for any account. Each tool then checks the plan of the workspace you name, so an account with no paid workspace sees zero spaces. That reads like a bug and is not one. Membership of one paid workspace resolves it.
list_spacesfilters out every workspace whose plan lacks MCP access, so the list comes back empty rather than erroring.
Three directions, three answers
"MCP" on its own is ambiguous here. Taskade sits on three separate paths, and each has its own availability:
| Direction | What it means | Availability |
|---|---|---|
| Inbound: Taskade as an MCP server | Claude, Cursor, or your own script reaches into your workspace | Live on every paid plan. Gated by the mcp.access plan entitlement |
| Outbound: a Taskade automation as an MCP client | A flow step lists and calls a remote MCP server's tools | Live on every plan that can run automations, including Free. The MCP Client connector carries no plan gate of its own |
| Outbound: a Taskade agent as an MCP client | An agent calls an external MCP server by itself | Not available. The code path sits behind a feature flag that is off on every production tier |
Outbound MCP runs in the automation engine, not the agent runtime.
Point the MCP Client connector at an https MCP server. Then call its tools as flow steps.
For agent access, configure the agent to trigger that automation. Agents do not call the server directly.
Production has no per-agent connector toolbox and no Space Connectors screen. Do not build against these surfaces.