Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Asana to Claude Code

Make Claude create and update tasks to keep projects current in Asana. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Asana to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Asana, you add a Asana MCP server: a small hosted service that exposes Asana's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Asana account. No API keys pasted into config files.

claude mcp add --transport http asana https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Asana once connected?

Full read-write Asana access lets Claude create tasks in the right project, set assignees and due dates, update custom fields, move tasks between sections, and post comments. The planning and status upkeep that used to mean clicking through the board happens where the work already lives, once you approve.

  • Create a task in a chosen project with an assignee, due date, and description
  • Update task fields like status, priority, or custom fields from a discussion
  • Move a task between sections or columns as it progresses
  • Add a comment or follow-up to a task to capture context
  • Set or change the assignee and due date on existing tasks
  • Create subtasks to break a larger task into tracked steps

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Asana access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Asana API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Asana changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Asana connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Asana connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Asana account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Asana's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Asana?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Asana account it signs in with. Revoking access is one click in Asana.

More on the Asana connector

Asana connector for claude.aiMonday.com + Claude CodeClickUp + Claude CodeJira + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us