Overview
MCP connects Taskade in three distinct ways. Choose the direction first.
- Hosted Taskade MCP: an external AI client connects to Taskade over HTTPS.
- Workspace MCP: an external AI client runs
@taskade/mcp-serverlocally. - MCP Client connector: a Taskade automation connects to an external MCP server.
Choose the right path
| Path | Direction | Transport and authentication | Best fit |
|---|---|---|---|
| Hosted Taskade MCP | AI client to Taskade | Streamable HTTP at https://www.taskade.com/mcp. OAuth 2.0 with PKCE or a Personal Access Token |
Remote clients and Taskade Genesis app source editing |
| Workspace MCP | AI client to Taskade | Local stdio through @taskade/mcp-server. Personal Access Token |
Desktop clients and REST API v1 operations |
| MCP Client connector | Taskade to another server | Streamable HTTP first, then SSE fallback. Optional bearer token | Calling an external MCP tool from an automation |
Access
Hosted Taskade MCP is available on every paid plan (Starter and above). The mcp.access feature row gates each workspace.
The MCP Client connector is shipped and ungated. It runs on every plan, including Free.
An agent cannot call an arbitrary MCP server in production. Configure the agent to trigger an automation that contains the MCP Client step.
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
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 in the automation engine. Add the MCP Client connector. List the remote server's tools. Then call the tool that you need.
The connector accepts https URLs only. It rejects embedded URL credentials, localhost and local hostnames, and internal IP literals. It does not follow redirects.
Each transport gets 20 seconds to complete its handshake. The connector tries Streamable HTTP first. If that handshake fails, it falls back to SSE. When the remote server requires a token, add the optional bearer token.