MCP

Hosted Taskade MCP

11 min readModel Context Protocol
MCP

Prefer a local server that wraps the full REST API v1? See Workspace MCP. Not sure which surface you need? See Which Taskade MCP do I want?.

The hosted Taskade MCP server connects MCP-compatible AI tools directly to your Taskade workspace.

From your client, browse the workspace. You can create, copy, complete, and restore projects. You can also edit tasks in existing projects.

This is the inbound direction: an AI client reaches into Taskade. For Taskade calling another MCP server, see Which Taskade MCP do I want?.

Task edits include create, update, complete, move, delete, dates, notes, assignees, and custom fields.

You can manage and prompt AI agents and edit Taskade Genesis app source code.

The toolset mirrors much of Action API v2. It grows with that API.

Availability
Hosted MCP is available on every paid plan (Starter and above). The mcp.access feature row gates each workspace.

See pricing for current plan details.

What you can do

  • Browse your workspace as a virtual filesystem. It holds projects, agents, automations, uploaded media, and app source code.
  • Read structured data. List folders, projects, templates, media, agents, automations, and tasks. Read a project's full task tree, custom fields, top-level blocks, members, and share link.
  • Create and orchestrate. Create projects from Markdown or from a template. Copy, complete, and restore projects, and turn on a project's share link. Create, update, and delete agents, attach projects or media as knowledge, and prompt an agent for its reply.
  • Edit your Taskade Genesis app source files (React components, styles, configuration) from your own IDE or AI tool.

What the hosted server cannot do

The hosted server currently cannot:

  • Create, edit, or run automations (the list is read-only)
  • Upload or delete media
  • Register webhooks. Use the Webhook Registration API instead

More tools land as the Action API v2 surface grows.

Requirements

  • A Taskade workspace with MCP access
  • Editor (collaborator) role or above in the workspace to write app source with write_file. Project and task tools run the same per-action permission checks as the Taskade app. A read-only role can browse, but it cannot modify
  • An MCP-compatible client such as:

Connecting your client

This is a hosted, remote MCP server, so you do not install software.

After you add the URL, an interactive client runs OAuth 2.0 with PKCE for you. The server also advertises dynamic client registration. You do not register an app by hand.

Header-controlled scripts and clients can use a Personal Access Token.

Production endpoint:

https://www.taskade.com/mcp

Taskade publishes OAuth discovery metadata at https://www.taskade.com/.well-known/oauth-protected-resource/mcp for clients that support automatic discovery.

Example: Claude Desktop / Claude Code

Add this to your MCP configuration file:

Json
{
  "mcpServers": {
    "taskade": {
      "type": "http",
      "url": "https://www.taskade.com/mcp"
    }
  }
}

Example: Cursor

In Cursor's MCP settings, add a new server with the URL https://www.taskade.com/mcp.

First-time OAuth authentication

The first time your client connects, Taskade MCP runs a standard OAuth2 flow:

  1. Let your MCP client discover the Taskade MCP server.
  2. Follow the browser redirect to Taskade.
  3. Sign in to Taskade.
  4. Authorize MCP access to your account.
  5. Let your client receive and store the token.

Do this once per client. Sign in with the Taskade account that can access the target workspace.

The MCP toolset

The server exposes workspace, project, task, agent, and app-editing tools. It also exposes a taskade://getting-started resource that an MCP client can read as a quickstart.

Most tools mirror an Action API v2 operation. MCP-native tools include inspect_space, read_project, list_automations, and write_file.

Most tools take a spaceId. Call list_spaces first to find it. That list is plan-filtered and paginated, so a page can be empty while more pages remain. Keep paginating until hasNextPage is false.

Browse & app editing

Tool What it does
list_spaces List the workspaces with MCP access that you belong to, with your role in each
inspect_space Read files and directories in a workspace's virtual filesystem - app/, projects/, agents/, automations/, media/. Use viewRange: [start, end] to return a specific line range from a file
write_file Create, edit, or delete files in your Taskade Genesis app's app/ directory. It can create a file, replace a substring, insert at a line, apply a unified diff, or delete a file

write_file refuses to delete a file while any app source still imports it. Remove or change those imports first. You can bring a deleted file back from the app's Version History.

Read workspace data

Tool What it does
list_folders The folders in a workspace (id, name). The first entry is the workspace itself
list_projects Projects in a workspace as structured JSON (id, name)
list_my_projects The projects you viewed recently, across workspaces. It needs no spaceId
get_project One project by id (id, name)
read_project A project's full contents - task tree with assignees, dates, tags
list_tasks Tasks in a project (id, text, completed, parent) with cursor pagination
list_blocks The top-level blocks of a project (id, text, completed) with cursor pagination
list_fields The custom fields on a project. Use a field id with set_task_field_value
list_project_members The members of a project (handle, display name)
get_share_link A project's edit and view share URLs, or null when sharing is off. It returns the check URL only for some workspace types
list_templates The project templates in a workspace (id, name)
list_media The media files in a workspace (id, kind)
list_agents The AI agents in a workspace (id, name)
list_automations The automations in a workspace (id, name)

Task writes

These tools mirror the Action API v2 task operations:

Tool What it does
create_task Add a task to a project, optionally under a parent task
update_task Edit a task's content
complete_task / uncomplete_task Check a task off, or reopen it
move_task Reorder a task or move it under a different parent
set_task_note / delete_task_note Set or clear a task's note
set_task_date / delete_task_date Set or clear a task's date
assign_task / unassign_task Assign a project member to a task, or remove them
set_task_field_value / delete_task_field_value Set or clear a custom field value on a task
delete_task Delete a task

If Google Calendar is connected on an eligible workspace, dates set with set_task_date can sync the same way as dates set in Taskade.

Create & orchestrate

Tool What it does
create_project Create a project in a workspace from Markdown
create_agent Create an AI agent (name + role instructions)
get_agent / update_agent / delete_agent Read, update, or delete an agent
prompt_agent Send a one-shot prompt to an agent and get its text reply
list_conversations / get_conversation Browse an agent's conversation history - get_conversation includes a Markdown transcript
add_knowledge_project / remove_knowledge_project Attach or detach a project as agent knowledge
add_knowledge_media / remove_knowledge_media Attach or detach a media file as agent knowledge. The file and the agent must be in the same workspace

If the new agent must read or change project data, pass "enableProjectTool": true to create_agent.

You can change this setting later with update_agent. This setting also enables the required knowledge support.

Tool names track the Action API v2 operations they mirror.

Project lifecycle

Tool What it does
create_project_from_template Create a project from a template. The template must be in the destination workspace
copy_project Copy a project that you can read into a workspace. It returns the new project id
complete_project / restore_project Archive a project as completed, or restore it. Both are idempotent
enable_share_link Turn on a project's share link and return its edit, view, and check URLs

enable_share_link returns an error if the share link is already on, or if your email is not verified.

The virtual filesystem

inspect_space presents each workspace as a directory tree:

workspace/
├── app/            # Your Genesis app source (writable via write_file)
├── projects/       # Tasks and documents (use read_project / list_tasks for structured reads)
├── agents/         # AI agent definitions
├── automations/    # Flows (read-only)
└── media/          # Uploaded files (read-only)

You can write files in the app/ directory only. Taskade rejects write_file against projects/, agents/, automations/, or media/. Use the structured tools in the earlier tables to create projects, edit tasks, and manage agents.

Example workflows

Refactor a component with Claude

"Open my 'Landing Page' workspace, look at app/src/App.tsx, and split the hero section into its own component. Keep the existing styling."

Claude will call list_spaces → inspect_space → write_file (twice) to create the new component file and update App.tsx.

Stand up a project and brief an agent

"Create a project called 'Q3 Launch' with a task per milestone from this outline. Attach it to my Research agent, then ask the agent to summarize the risks."

The client calls create_project, add_knowledge_project, and prompt_agent. No browser tab needed.

Audit your app for accessibility

"Check every file in app/src/ for missing alt text, ARIA labels, and keyboard handlers. Suggest fixes but do not apply them yet."

The client reads your files with inspect_space. It shows you a report before you approve the edits.

Tips and gotchas

  • Read before you edit. Ask your client to inspect a file first. An edit against a stale view can fail or produce an unexpected result.
  • One workspace at a time. Tools take a spaceId. Before you issue a command, point your client at the right workspace.
  • A write goes live. Each successful write_file commits the change and starts a new build. On an app that is already live, the default setting publishes that build to the live domains by itself. If the app owner chose Manual Updates in the publish settings, press Publish in Taskade to make the change live.
  • Access is per workspace. Select a workspace that has MCP access.
  • prompt_agent runs the agent. It uses the agent's configured model and consumes AI credits. Treat it as a real prompt, not a preview.

When to use MCP vs. Taskade EVE

Both MCP and Taskade EVE (Taskade's in-product AI assistant) can build and orchestrate. Use whichever fits your workflow:

Use Taskade EVE when… Use MCP when…
You are already inside Taskade You work in your IDE
You want to build and manage tasks, automations, and an app in one conversation You script operations across projects, agents, and app code
You build from a prompt end-to-end You want to use a specific model or tool
You prefer a conversational flow You want precise, file-level control

If Taskade EVE does not fit your workflow, use MCP with your preferred model, prompts, and keybindings.

Troubleshooting

"MCP access is not available on this workspace's current plan."
The workspace does not have MCP access. Examine the current access details with the workspace owner.

"Access denied: you are not a member of this space."
Your account is not a member of the workspace. Make sure that the workspace ID is correct, or request an invitation.

"Access denied: your role … does not have write access. Requires collaborator or above."
write_file requires collaborator or above. A read-only role can still browse.

OAuth flow keeps looping.
Sign in to the correct Taskade account in your browser. Then clear the stored client credentials and reconnect.

Feedback

The hosted MCP is in active development. Your feedback shapes what we ship next. If something is missing, broken, or confusing, tell us.

TL;DR: Add https://www.taskade.com/mcp to your MCP client and sign in. The server creates and manages projects, edits tasks, manages and prompts agents, and edits Taskade Genesis app source in workspaces with MCP access.

For a local server that wraps REST API v1, see Workspace MCP.

PreviousWorkspace MCP: AdvancedNextRun Your Live App by Talking to Claude