Connect

Agents and External MCP Servers

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

Overview

MCP (Model Context Protocol) works in two directions. An outside AI tool can connect into Taskade, or Taskade can call out to the MCP server of another service. This page covers the second direction, and where your agents fit in it.

TL;DR: Taskade calls out to an MCP server through an automation. The MCP Client connector points an automation at a remote MCP server and runs its tools as steps, on every plan. In production, an agent cannot call that server on its own, so the agent hands its answer to the automation. Setup steps: MCP Client Integration.

Know the Two Directions

INBOUND: an AI tool works in Taskade
┌──────────────┐     ┌──────────────┐
│ Claude,      │ ──▶ │ Your Taskade │
│ Cursor       │     │ workspace    │
└──────────────┘     └──────────────┘

OUTBOUND: Taskade calls a service
┌──────────────┐ ──▶ ┌──────────────┐
│ A Taskade    │     │ External MCP │
│ automation   │ ◀── │ server       │
└──────────────┘     └──────────────┘
Direction How it runs Plan
Inbound An AI tool connects to the Taskade MCP Server Every paid plan
Outbound from an automation The MCP Client connector runs as a step Every plan, Free included
Outbound from an agent alone Not available in production Off on every plan in production

Your plan sets how many automation runs you get in each billing period. See Pricing for the run limits.

Let an Agent Hand Off to an Automation

An agent makes the judgment call. The automation carries the call to the outside server. The result comes back into the next step:

┌──────────────────────────────┐
│  Your agent                  │
│  reads a project, decides    │
└──────────────┬───────────────┘
               │  passes its answer
               ▼
┌──────────────────────────────┐
│  Automation                  │
│  MCP Client: Call Tool       │
└──────────────┬───────────────┘
               │  calls a tool
               ▼
┌──────────────────────────────┐
│  External MCP server         │
└──────────────┬───────────────┘
               │  the result
               ▼
┌──────────────────────────────┐
│  Next step: write to a       │
│  project, or notify          │
└──────────────────────────────┘

The automation holds three parts:

  • The Agent Tool trigger, so the agent can start the automation
  • An MCP Client step with the address of the server, and a token if the server asks for one
  • A Call Tool action that takes the answer of the agent as its input

Setup steps for each part: MCP Client Integration.

Use It to Skip Copy and Paste

The outbound direction reads and writes data where it already lives:

You want The automation does
Research from a wiki in another tool Calls the wiki server and writes the text into a project
File an issue in the tracker of your team Calls the tracker server with the details from an agent
Combine two services Reads from one server, asks an agent, writes to another server

For a service with no MCP server, use the 100+ integrations in the same automation.

Frequently Asked Questions

Can Taskade connect out to external MCP servers?

Yes, through automations. The MCP Client connector holds the address of the server and calls its tools as steps. In production, an agent cannot reach a server on its own, so let it hand the work to an automation.

Which plan includes MCP?

The MCP Client connector works on every plan, and your plan sets how many automation runs you get. The hosted Taskade MCP server, which lets other AI tools connect into Taskade, needs a paid plan. See Pricing.

How can my agents work with outside tools today?

Agents use their built-in tools, such as web search, code, and file analysis. For an MCP server or one of the 100+ integrations, put the call in an automation that the agent starts.

Was this helpful?