Taskade MCP Server
Connect Claude, ChatGPT, Cursor, VS Code, and other AI tools to your Taskade workspace with one URL and a Taskade sign-in.
Connect
Overview
The Taskade MCP server lets an AI tool work in your Taskade workspace. MCP (Model Context Protocol) is an open standard that AI tools use to reach other apps. Connect once, and your AI tool can read and update your work for you.
TL;DR: Paste
https://www.taskade.com/mcpinto Claude, ChatGPT, Cursor, or VS Code as a custom connector, then sign in with Taskade. Your AI tool can then read and update your projects, tasks, agents, and Taskade Genesis apps. Hosted MCP works on every paid plan. On Free, run the open-source server on your computer.
┌──────────────────────────────┐
│ Your AI tool │
│ Claude · ChatGPT · Cursor │
└──────────────┬───────────────┘
│ 1. Add the URL
▼
┌──────────────────────────────┐
│ Taskade sign-in page │
│ 2. You sign in and allow │
└──────────────┬───────────────┘
│ 3. Tools appear
▼
┌──────────────────────────────┐
│ Your Taskade workspace │
│ projects · tasks · agents │
│ automations · app files │
└──────────────────────────────┘
Before You Start
- What you need: a Taskade workspace on a paid plan, and an AI tool that can add an MCP connector.
- Time: about 2 minutes.
- On the Free plan: run the open-source server on your computer instead.
Connect Your AI Tool
Step 1: Copy the server URL
Copy this address:
https://www.taskade.com/mcp
The address is for your AI tool, not for your browser. If you open it in a browser, you see a short setup page. That is normal. The page has a Copy button for the URL, three setup steps, and a table that shows where to paste the URL in common AI tools.
Step 2: Add Taskade to your AI tool
Paste the URL where your tool adds a custom connector or a remote MCP server:
| AI tool | Where to paste the URL |
|---|---|
| Claude (desktop and web) | Connectors → Add custom connector. Name it Taskade. |
| ChatGPT | Turn on developer mode, then create a connector. Choose OAuth as the sign-in. |
| Claude Code | Run one command. See Install in Claude Code. |
| Cursor | Select Add to Cursor in Settings → API, or add the URL to .cursor/mcp.json. See Connect from Cursor. |
| VS Code | Select Add to VS Code in Settings → API. Or run MCP: Add Server, choose HTTP, and paste the URL. |
AI tools rename these menus between releases. If you cannot find them, search the help of your tool for "custom connectors".
If you work in a terminal, one command adds Taskade to Claude Code, Codex, Cursor, or VS Code. See Connect with one command.
Step 3: Sign in to Taskade
Your AI tool opens a browser window. Sign in to Taskade and allow access. You put no password or key in a config file.
Step 4: Check the connection
Ask your AI tool for a first read:
List my Taskade workspaces. Do not change anything.
Why this works: "Do not change anything" keeps the first test read-only.
You are done when your AI tool lists your workspaces that are on a paid plan. A Free workspace does not show in the list. Your AI tool shows a short note about the plan in its place.
Install in Claude Code
Claude Code adds the server with one command:
claude mcp add --transport http taskade https://www.taskade.com/mcp
Then type /mcp, select taskade, and sign in.
To add the Taskade skills too, install the plugin instead. The skills tell Claude which tool fits each job:
claude plugin marketplace add taskade/mcp
claude plugin install taskade@taskade
Another agent that reads skills can install the Taskade skill from the site root:
npx skills add https://www.taskade.com
Use the site root in that command. The form that ends in /SKILL.md installs nothing. To read the skill yourself, open taskade.com/SKILL.md.
Connect from Cursor
Add this block to .cursor/mcp.json:
{
"mcpServers": {
"taskade": {
"type": "http",
"url": "https://www.taskade.com/mcp"
}
}
}
Save the file. Open the MCP settings of Cursor, find taskade, and sign in when Cursor asks.
Connect With a Personal Access Token
If your AI tool cannot open a browser, or reads only a config file, use a token:
- Open Settings → API in Taskade. Create or copy a personal access token.
- Under MCP connection, open Advanced: use a personal access token.
- Select Connect Cursor or Connect Claude. Taskade copies a configuration with a token placeholder.
- Replace
<paste-your-token-here>with your token. - Paste the
taskadeentry into the MCP config file of your tool, for example.cursor/mcp.jsonin Cursor. Save the file. - Restart the tool.
Warning: Keep that config file private, and do not commit it to a code repository. It now holds your token, and the token can do everything your account can do.
Work You Can Hand to Your AI Tool
Ask in plain language. Your AI tool picks the right Taskade tool:
| Area | Your AI tool can |
|---|---|
| Workspaces and folders | Browse every place your account can open |
| Projects | Read, create, copy, rename, complete, and restore. Create one from a template. Add or rename a custom field. Get or turn on a share link |
| Tasks | Create, update, complete, move, assign, and delete. Set dates, notes, and custom fields |
| Agents | Create, update, and delete. Ask an agent a question. Read past chats. Add or remove knowledge |
| Automations | List them. Run one that is On and starts with the Agent Tool trigger. Read its recent runs |
| Taskade Genesis app | Read and edit the app files |
Some requests to try:
| You ask | What happens |
|---|---|
| "Turn these meeting notes into a project." | A new project with tasks appears in your workspace. |
| "Add three follow-ups to the Q2 roadmap, due Friday." | The tasks land in that project with their dates. |
| "Ask my analyst agent for the top three risks." | You get the answer of the agent in your AI tool. |
| "Why did the weekly report automation fail?" | Your AI tool reads the recent runs and the failed step. |
| "Add a status filter to the dashboard." | Your AI tool edits the files of your app. |
Note: A request to run an automation or to ask an agent is a real action. An automation run counts toward the monthly automation runs of your plan. Both can use AI credits. An automation run can also send email or act in a connected app.
Your AI tool sees only what your Taskade account can see. Editing app files needs Editor access or above. Reading the run history needs edit access to automations. A long list comes back in pages, so ask for the next page when a list looks short.
Jobs That Stay in Taskade EVE
MCP works with what already exists in your workspace, including edits to a live app. Open Taskade and ask Taskade EVE for these jobs:
- Create or edit an automation
- Build a new app, or publish an app that is not live yet
- Set who can use an app
Your AI tool can write the request for you. Paste it into Taskade EVE.
Pick Hosted or Open-Source
Taskade gives you two MCP servers. Most people want the hosted one:
| Hosted server | Open-source server | |
|---|---|---|
| Where it runs | Taskade, at https://www.taskade.com/mcp |
Your own computer |
| Sign-in | Taskade sign-in in the browser, or a token | A personal access token |
| Plan | Every paid plan | Every plan, Free included |
| Edits app files | Yes | No |
The hosted server checks the plan of each workspace. If your account and all your workspaces are on Free, Settings → API shows a Pro badge beside MCP connection. Its buttons then open the upgrade window. A Free member of a paid workspace keeps the plain copy button.
The other direction, where Taskade calls out to an MCP server, runs in an automation on every plan. See MCP Client Integration.
Run the Open-Source Server on Any Plan
The open-source taskade/mcp server runs on your own computer, and your AI tool starts it. It signs in with a personal access token, so it works on Free too.
- What you need: Node.js 18 or later, and a token from Settings → API.
Add this block to the Claude Desktop config file (claude_desktop_config.json). Cursor takes the same block in .cursor/mcp.json:
{
"mcpServers": {
"taskade": {
"command": "npx",
"args": ["-y", "@taskade/mcp-server"],
"env": {
"TASKADE_API_KEY": "your-api-key-here"
}
}
}
}
Restart the tool. You are done when Taskade tools show in its tools menu.
The open-source server reaches what the public Taskade API reaches: workspaces, folders, projects, tasks, agents, templates, and media. It can also generate an agent from a description and turn on public access for an agent. It does not edit app files.
To serve it at a web address, follow the HTTP mode steps in Workspace MCP. The same repository holds @taskade/mcp-openapi-codegen, which builds MCP tools from any OpenAPI file: npx @taskade/mcp-openapi-codegen --spec https://api.example.com/openapi.json.
Frequently Asked Questions
Why do I see a setup page or a 401 error at the server URL?
Both are normal. A browser shows a setup page at https://www.taskade.com/mcp. A tool that sends no sign-in gets a 401 answer that asks it to sign in. Add the URL to your AI tool and sign in there. Do not change the URL.
Can I use the hosted server on the Free plan?
No. The hosted server works on every paid plan. On Free, run the open-source taskade/mcp server on your computer with a personal access token. An automation can still call an outside MCP server on Free.
Which AI tools work with the Taskade MCP server?
Claude (desktop and web), ChatGPT, Claude Code, Cursor, VS Code, Windsurf, n8n, and any tool that supports MCP. VS Code supports MCP natively, so you need no extension.
Can my AI tool edit my Taskade Genesis app?
Yes. Your AI tool can create, edit, and delete files in the app/ folder of the app. You need Editor access or above. On the default publish setting, a saved edit can go live at once. Ask your AI tool to read a file before it changes it. See MCP Connectors for the details.
Do I need a second Taskade account to connect Claude?
No. Sign in with the Taskade account you already have. Your AI tool works in the same workspaces.
Can Taskade call out to another MCP server?
Yes, through an automation. The MCP Client connector calls the tools of a remote MCP server as automation steps, on every plan. In production, an agent cannot call an outside MCP server on its own. Let it hand the work to an automation.
Related guides
- MCP Connectors. A map of every MCP path in Taskade
- MCP Client Integration. Call another MCP server from an automation
- Agents and External MCP Servers. How agents use outside MCP tools
- Developer API. Other ways to reach Taskade from code
- Hosted Taskade MCP developer docs. The exact config for every client, and the full tool list
- Taskade skills. Skills that tell your AI tool how to do one job in Taskade, such as fixing an app