Taskade uses MCP in two directions across three distinct paths. Choose by what starts the connection.
Inbound: an AI client reaching into Taskade
| I want to… | Use | Where / auth |
|---|---|---|
| Have Claude read and write my tasks | Workspace MCP or Hosted Taskade MCP | Local stdio with a Personal Access Token, or hosted HTTPS with OAuth 2.0 or a Personal Access Token |
| Orchestrate my workspace from my IDE and edit Taskade Genesis app source | Hosted Taskade MCP | https://www.taskade.com/mcp |
Hosted MCP capabilities: Hosted Taskade MCP creates projects, edits tasks, manages and prompts agents, and edits Taskade Genesis app source. Use Workspace MCP for REST API v1 operations such as media upload.
Hosted Taskade MCP is available on every paid plan (Starter and above).
Outbound: Taskade calling another MCP server
| I want to… | Use | Where / auth |
|---|---|---|
| Call another MCP server's tools from Taskade | MCP Client connector | An automation step with the remote server's HTTPS URL and optional bearer token |
The outbound direction runs through automations, not through the agent runtime.
The MCP Client connector is shipped and ungated. It runs on every plan, including Free.
An agent cannot access an arbitrary MCP server directly in production.
Configure the agent to trigger an automation that contains an MCP Client step. The automation returns the result.
For services without MCP, use Taskade's 100+ native integrations, including Slack, Gmail, and Shopify.