Taskade works with the Model Context Protocol (MCP) in two directions. An AI client can work in your workspace, and a Taskade automation can call the tools of another MCP server.
Page type: Concept. Use it to pick the page that fits your task.
TL;DR: To use Taskade from Claude, Codex, Cursor, VS Code, or ChatGPT, connect the client to the hosted Taskade MCP at
https://www.taskade.com/mcp(every paid plan). To call another MCP server from Taskade, use the MCP Client connector in an automation (every plan).
How the three paths work
MCP is an open protocol that lets an AI client discover and call the tools of a server. Taskade has three MCP paths. Choose the direction first:
INTO TASKADE OUT OF TASKADE
┌───────────────────────┐ ┌───────────────────────┐
│ External AI client │ │ Taskade automation │
└─────┬───────────┬─────┘ └───────────┬───────────┘
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌───────────────────────┐
│ Hosted │ │Workspace │ │ MCP Client connector │
│ MCP │ │MCP, local│ └───────────┬───────────┘
└────┬─────┘ └────┬─────┘ ▼
▼ ▼ ┌───────────────────────┐
┌───────────────────────┐ │ External MCP server │
│ Taskade workspace │ └───────────────────────┘
└───────────────────────┘
Most readers want the hosted server. Use the local server only when you need a REST API v1 operation that the hosted server does not expose.
| Path | Direction | Transport and sign-in | Best fit |
|---|---|---|---|
| Hosted Taskade MCP | Into Taskade | Streamable HTTP. OAuth 2.0 with PKCE, or a personal access token | Remote clients and app source edits |
| Workspace MCP | Into Taskade | Local stdio through @taskade/mcp-server. A personal access token |
Desktop clients and REST API v1 calls |
| MCP Client connector | Out of Taskade | Streamable HTTP, then SSE. An optional bearer token | An external MCP tool in an automation |
Connect a client
Each client has its own config. The hosted MCP page gives the exact block for each one.
| Client | Setup |
|---|---|
| Claude (desktop and web) | Add a custom connector |
| Claude Code | The Taskade plugin, or one claude mcp add command |
| Codex | codex mcp add with the server URL, then codex mcp login |
| Cursor | mcp.json with the server URL |
| VS Code | .vscode/mcp.json with servers |
| ChatGPT | A custom connector in developer mode |
| Windsurf | mcp_config.json with serverUrl |
| Other clients and scripts | A token header, or the mcp-remote bridge |
| Any agent that reads skills | npx skills add https://www.taskade.com, or read https://www.taskade.com/SKILL.md |
Access
Each MCP path has its own plan rule.
| Path | Plan | Rule |
|---|---|---|
| Hosted Taskade MCP | Every paid plan (Starter and above) | A Free workspace does not appear in list_spaces. The response adds hiddenForPlan and a hint |
| Workspace MCP | The plan rules of each API call | Each tool keeps the access rules of the API operation that it calls |
| MCP Client connector | Every plan, Free included | Runs as a step in an automation |
In production, an agent cannot call an arbitrary MCP server directly. To give an agent a remote MCP tool, have the agent trigger an automation that contains the MCP Client step.
What MCP leaves to Taskade EVE
The hosted server reads and changes what exists in a workspace. It edits the source of an existing app, and an edit to a live app can go live on its own. It cannot create or edit an automation, or build a new app. It also cannot publish an app that is not live yet, or set who can use an app. Send those jobs to Taskade EVE inside Taskade.
run_flow and prompt_agent are real actions. They count toward the plan and can use AI credits.
Authentication
The hosted server supports OAuth 2.0 with PKCE. It publishes protected-resource metadata at:
https://www.taskade.com/.well-known/oauth-protected-resource/mcp
A request with no token gets 401 and a WWW-Authenticate: Bearer header. That response is expected. Header-controlled clients can use a personal access token.
The local Workspace MCP server reads a personal access token from TASKADE_API_KEY.
Use outbound MCP safely
Outbound MCP runs as a step in an automation. Add the MCP Client connector, list the tools of the remote server, then call the tool that you need.
| Rule | Detail |
|---|---|
| URL | https only. The connector rejects credentials in the URL, localhost and other local host names, and private IP addresses. |
| Redirects | The connector does not follow redirects. |
| Handshake | Each transport gets 20 seconds. The connector tries Streamable HTTP first, then SSE. |
| Token | Add the optional bearer token when the remote server requires one. |
Set this up with your coding agent
Paste this block into your coding agent to connect it.
Connect to the hosted Taskade MCP server at https://www.taskade.com/mcp over Streamable HTTP. If you support interactive sign-in, use OAuth 2.0 with PKCE and dynamic client registration. If you can only send headers, send "Authorization: Bearer <token>" with a personal access token from https://www.taskade.com/settings/api. The workspace must be on a paid Taskade plan. First call list_spaces and page until hasNextPage is false. Then call inspect_space on one workspace and report what you can see. Do not write anything until I confirm.
Next steps
- Hosted Taskade MCP: connect Claude, Codex, Cursor, VS Code, ChatGPT, or another client.
- Which Taskade MCP do I want?: pick a path by what you want to do.
- Workspace MCP: run the local server that wraps REST API v1.
- MCP Client connector: call another MCP server from an automation.