# How to connect Asana to Claude

> Use Claude with Agent200 for read-only Asana task briefings. Check owners, deadlines and completion states with the user's own connection.

- Page: https://www.agent200.com/connectors/asana/framework/claude/
- Connector: [Asana](https://www.agent200.com/connectors/asana.md)
- Framework: Claude
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Asana to Claude with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/asana/framework/claude/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Asana is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands.
4. The first Asana request returns an authorization link if the user has not connected Asana yet: show it to them and continue once they have approved access on Asana's own page.
5. Check it works with this request: "Read the Asana task I identify and summarize its owner, due date, completion state and next steps stated in its description. Ask me for the task ID if it is missing. Do not change anything."
   What should come back:
   - The selected task is identified clearly.
   - The answer uses only the task information returned, including owner, due date and completion state when available.
   - Missing fields and access failures are reported without guessing; no Asana records are changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Asana, then retry.

## Overview

Use Claude to turn a selected task into a concise briefing before a meeting. Start with one task whose ID you already know, so the first check does not depend on search eligibility. Separate what the task says from questions you still need to ask its owner.

Begin with one task the connected user can access. The Asana catalogue on this page is read-only: a briefing does not create, assign, complete or delete work. Discover the available tools and use their returned schemas before running the test.

Product reference: [Claude documentation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). For Asana task fields and optional field selection, see [Asana's task-read reference](https://developers.asana.com/reference/gettask).

- **Connector:** [Asana](https://www.agent200.com/connectors/asana/)
- **Works with:** Claude · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/asana/framework/claude/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Asana enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Asana account.** They approve access once, on Asana's own page.
- **Claude, with custom MCP servers allowed.** Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.

## Connect Asana to Claude

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Asana and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open Connectors in Claude

On a Free, Pro, Max or Ultra plan, go to **Customize > Connectors**. On Team or Enterprise, an Owner goes to **Organization settings > Connectors**; members then find the connector under Customize > Connectors.

### Step 3: Add a custom connector

Select **Add**, then **Add custom connector**. Enter a name, Agent200, and the remote MCP server URL, then choose **Continue**.

### Step 4: Send your key as a request header

Under Authentication choose **No sign-in**. Open **Request headers**, pick `authorization`, enter `Bearer` followed by a space and your key, mark it Required and choose **Add**. Claude sends the value exactly as typed.

File `Add custom connector`:

```text
Remote MCP server URL:  https://api.agent200.com/mcp/
Authentication:         No sign-in
Request header name:    authorization
Value:                  Bearer YOUR_AGENT200_API_KEY
```

### Step 5: Turn it on in a chat

In a chat, select **+ > Connectors** and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.

### Step 6: Connect your Asana account

The first time you ask Claude for something in Asana, Agent200 returns an authorization link. Open it and approve access on Asana's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.

## Test your connection

Ask: "Read the Asana task I identify and summarize its owner, due date, completion state and next steps stated in its description. Ask me for the task ID if it is missing. Do not change anything."

What should come back:

- The selected task is identified clearly.
- The answer uses only the task information returned, including owner, due date and completion state when available.
- Missing fields and access failures are reported without guessing; no Asana records are changed.

If authorization is requested, complete it with the intended Asana account. If a tool or field is unavailable, report it and check the actual tool definition. Workspace task search has separate premium access requirements.

## Asana tools Claude can call

- **Read a task** (`asana_get_task`, read): Retrieve an Asana task's details, including its description, assignee, due date and completion status.
- **Search tasks** (`asana_search_tasks`, read): Search workspace tasks by text and filters. Requires Asana premium search access.
- **List project tasks** (`asana_list_project_tasks`, read): List the tasks in a selected project, then read individual tasks for descriptions, ownership and deadlines.
- **List subtasks** (`asana_list_subtasks`, read): List the subtasks of a parent task so your agent can inspect the smaller work items behind it.
- **List projects** (`asana_list_projects`, read): List projects in a workspace to find the project relevant to a request.
- **Read a project** (`asana_get_project`, read): Read a project's name and description to understand its purpose and context.

## How it works

1. **You ask Claude.** In your own words, for something in Asana.
2. **Claude picks a tool.** It sees the Asana tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Asana connection, within the tools and scopes your project allows.
4. **Claude answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Asana account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Asana enforces what its API grants.

## Troubleshooting

### The task is missing or cannot be read

Confirm the task ID and that the connected Asana user can open it. An access error is not an empty task. Ask for the right task rather than guessing an ID or claiming a result.

### The answer omits the owner or deadline

Check the fields actually returned by the tool. An omitted field does not prove a task is unassigned or has no due date. Report unavailable information explicitly.

### Task search fails even though a task read works

Asana workspace task search requires premium eligibility and may lag recent changes. Use an identified accessible task for the first test. See [Asana’s search requirements](https://developers.asana.com/reference/searchtasksforworkspace).

## FAQ

### Can I use this guide without Asana premium search?

Yes: use an identified task for the first read. Workspace search has separate premium eligibility requirements. A search access error does not mean you cannot read a task that your account can open.

## Use Asana with another framework

- [Asana + ChatGPT](https://www.agent200.com/connectors/asana/framework/chatgpt.md)
- [Asana + Claude Code](https://www.agent200.com/connectors/asana/framework/claude-code.md)
- [Asana + Muse](https://www.agent200.com/connectors/asana/framework/muse.md)
- [Asana + Grok Bot](https://www.agent200.com/connectors/asana/framework/grok-bot.md)
- [Asana + OpenAI Dots](https://www.agent200.com/connectors/asana/framework/openai-dots.md)
- [Asana + Claude Duet](https://www.agent200.com/connectors/asana/framework/claude-duet.md)
- [Asana + Hermes Agent](https://www.agent200.com/connectors/asana/framework/hermes-agent.md)
- [Asana + OpenClaw](https://www.agent200.com/connectors/asana/framework/openclaw.md)
- [Asana + LangGraph](https://www.agent200.com/connectors/asana/framework/langgraph.md)
- [Asana + OpenAI Agents SDK](https://www.agent200.com/connectors/asana/framework/openai-agents-sdk.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
