Connect Asana to Claude Code

Search, file and update Asana tasks, and read the projects, sections and people around them. Add Toolspoke to Claude Code once and it can use 13 Asana actions. Your Asana credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Asana and connect it

    Add Asana to a project in your Toolspoke workspace.

    Personal access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Personal access token
    Asana → your profile photo → My settings → Apps → Manage developer apps → Personal access tokens. The token acts as you, with exactly your own Asana permissions.
  3. Choose what Claude Code may do

    All 13 actions start on. Switch off any of the 4 actions that change something in Asana, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Asana actions that only read, so they are safe to try first.

  • Enumerate the tasks of one project, section or tag, or one person's tasks in a workspace
  • List the projects in a workspace, optionally narrowed to one team
  • List the sections of one project, in board or list order
  • List the workspaces and organizations this token can see

What Claude Code can do in Asana

9 actions read and 4 write.

Reads

  • Search tasks

    Search a workspace's tasks by free text and by any combination of assignee, project, section, tag, completion state and date window. This is the open-ended read, reach for it first, and use list_tasks only when you already know the exact project, tag or section to enumerate. Results are ordered by the sort you ask for and capped at 100; Asana's ordinary offset paging does not work here, so narrow the query rather than trying to page through it. Note that Asana restricts this endpoint to premium workspaces and answers a free one with a 402.

  • List tasks

    Enumerate the tasks of one project, section or tag, or one person's tasks in a workspace. IMPORTANT: Asana refuses a bare call, you must pass project, section or tag, OR pass assignee together with workspace_gid. Passing assignee without workspace_gid, or workspace_gid without assignee, is rejected with a 400 that reads like a malformed request rather than a missing filter. For anything more open-ended than that, use search_tasks.

  • Get task

    Fetch one task in full: its description, dates, assignee, followers, tags, project memberships and custom field values. Use it after search_tasks or list_tasks when you need the actual content of a task rather than its summary. Comments are not part of a task record, they are stories, and there is no story listing in this connector.

  • List projects

    List the projects in a workspace, optionally narrowed to one team. Archived projects are excluded unless you ask for them. This is how you find the project gid that list_tasks, list_sections and create_task take.

  • Get project

    Fetch one project in full, including its description, owner, team, dates, current status and custom field settings. Use list_projects to find the gid first.

  • List sections

    List the sections of one project, in board or list order. Sections are the columns of a board and the headings of a list, and their gids are what list_tasks takes as `section`.

  • List workspaces

    List the workspaces and organizations this token can see. Call it first when you do not know which workspace to act on, and to find out whether the connection reaches anything at all, an empty list means the token is valid but belongs to no workspace. The gid returned here is what every workspace_gid argument takes.

  • List users

    List the people in a workspace, or in one team, with their names and email addresses. Use it to find the user gid that create_task and update_task take as `assignee`, and that search_tasks filters on.

  • List tags

    List the tags defined in a workspace, with their gids and colours. Tags are how Asana marks work across projects, and these gids are what search_tasks and list_tasks filter on and what create_task applies.

Writes

  • Create task

    File a new task. Asana needs somewhere to put it: pass either project_gids or workspace_gid, a task with neither is rejected. assignee takes a user gid, an email address, or the literal "me". Returns the created task including its gid and permalink URL.

  • Update task

    Change fields on an existing task: rename it, rewrite the description, move the due date, reassign it or reparent it. Pass only the fields you want changed; anything omitted is left alone. Use complete_task to tick a task off, and note that projects and tags cannot be changed here. Asana treats those as create-only on the task record.

  • Complete task

    Mark a task complete, or reopen one by passing completed as false. This is the same PUT /tasks/{gid} endpoint update_task uses, separated out so completing a task is one unambiguous call rather than a field an agent has to remember to set. Completing a task in Asana is reversible and notifies its followers.

  • Add comment

    Post a comment on a task. Asana calls comments stories, and this creates one of resource_subtype comment_added on the task's story collection. Send either text or html_text, not both, html_text takes Asana's restricted HTML and must be wrapped in a <body> element. Everyone following the task is notified.

Asana in Claude Code: questions

Does Claude Code see my Asana credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Asana?

Yes. Each of the 13 actions can be switched off for a project. Turn off the 4 that change something and Claude Code can only read.

Will 13 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Asana action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Asana call does not run in a sandbox, so it bills nothing.

Try Asana in Claude Code

Free to start, and tool calls cost nothing on any plan.