Taskade Genesis

MCP Connectors

Updated 2026-11-03·6 min read·View as Markdown

Overview

The Model Context Protocol (MCP) is an open standard that lets AI tools use the data and actions of other apps. Taskade uses MCP in two directions. Your AI tool can work in your workspace, and your automations can call other MCP servers.

TL;DR: The hosted Taskade MCP server lets Claude, ChatGPT, Cursor, or VS Code work in your workspace on every paid plan. Setup: Taskade MCP Server. The other direction runs in an automation, where the MCP Client connector calls a remote MCP server on every plan.

Taskade Genesis MCP integrations

Keep the MCP Paths Apart

Each MCP path has its own setup and its own plan rule. Pick the path by what starts the work:

AI TOOL STARTS       TASKADE STARTS
┌────────────────┐   ┌────────────────┐
│ Claude, Cursor │   │ An automation  │
└───────┬────────┘   └───────┬────────┘
        ▼                    ▼
┌────────────────┐   ┌────────────────┐
│ Hosted MCP or  │   │ MCP Client     │
│ open-source    │   │ connector      │
└───────┬────────┘   └───────┬────────┘
        ▼                    ▼
┌────────────────┐   ┌────────────────┐
│ Your workspace │   │ External MCP   │
│                │   │ server         │
└────────────────┘   └────────────────┘
Path What it does Plan
Hosted MCP server Your AI tool connects to https://www.taskade.com/mcp and works in your workspace Every paid plan
Open-source server The taskade/mcp server runs on your computer with a personal access token Every plan, Free included
Automation calls out An automation uses the MCP Client connector to call a remote MCP server Every plan, Free included
Agent calls out alone An agent calls a remote MCP server with no automation Not available in production

Call Another MCP Server from Taskade

Use these steps when Taskade must call out to another MCP server.

Step 1: Open Automations

Open the Automations tab in your workspace.

Step 2: Add the MCP Client connector

Add a step and pick the MCP Client connector. Enter the address of the remote server.

Step 3: Save and run the automation

Save the automation. Run it, so the step can list the tools on that server and call the one you pick.

You are done when the run shows the result of the tool. In production, an agent cannot reach an outside MCP server on its own. Let the agent decide, then hand the call to an automation. Full setup: MCP Client Integration.

Reach Workspace DNA and Your App

Over the hosted server, your AI tool works with the three parts of Workspace DNA, and with the app built on top of them:

Part Your AI tool can
Projects (Memory) Read, create, and copy projects. Add and edit tasks
AI agents (Intelligence) Create, update, and ask agents. Add knowledge
Automations (Execution) List them, run one that starts with the Agent Tool trigger, read its runs
Taskade Genesis app, built on top Read and edit the app files

Edit Your Taskade Genesis App Over MCP

Your AI tool can change the source files of a Taskade Genesis app. It can write only inside the app/ folder:

  • Read a file before you edit it. An edit against an old copy can fail.
  • Create a file, replace text, insert at a line, or apply a patch.
  • Delete a file that nothing imports. Taskade refuses the delete while an import still points at it.
  • Bring back a deleted file from the version history of the app.

A saved edit is final, not a draft. The app rebuilds, and an app on the default publish setting goes live with the change. You do not press Publish again.

Some app jobs stay in Taskade. MCP cannot build a new app, or publish an app that is not live yet. It also cannot set who can use an app, or create or edit an automation. Ask Taskade EVE for those.

Plans and Credits

Path Free Paid plans
Hosted MCP server No Yes
Open-source server Yes Yes
Automation calls out Yes Yes
Agent calls out alone (production) No No

There is no separate MCP fee. An automation run that your AI tool starts counts toward the monthly automation runs of your plan. Runs and agent questions can use AI credits, the same as in Taskade. See Pricing.

Frequently Asked Questions

Which plans include MCP?

The hosted Taskade MCP server is on every paid plan. The open-source taskade/mcp server on your computer works on every plan, Free included. An automation can call a remote MCP server on every plan, Free included. In production, an agent cannot call a remote MCP server on its own on any plan.

Do MCP calls cost credits?

There is no separate MCP fee. When your AI tool runs an automation or asks an agent, that work counts toward your plan. It can use AI credits, the same as in Taskade.

Is MCP secure?

Yes. Connections use encrypted HTTPS. Your AI tool signs in as you, with a Taskade sign-in or a personal access token, so it reaches only what your account can see. Remove the connector or revoke the token to cut off access.

How do built-in agent tools differ from MCP?

Built-in tools such as web search, code, and file analysis run inside Taskade and give your agents abilities. MCP lets a separate AI tool, such as Claude, work with your Taskade data from the outside.

Can an AI tool reach my Taskade Genesis apps over MCP?

Your AI tool connects to your workspace. It can reach the projects, tasks, and agents behind your apps, and it can edit app files. The published app stays a normal web app for your visitors.

Does MCP work with every AI model?

Yes. MCP does not depend on the model. Any AI tool that speaks MCP can connect to Taskade, whatever model it runs.

Was this helpful?