Asana + OpenClaw
How to connect Asana to OpenClaw
Use OpenClaw with Agent200 for read-only Asana task briefings. Check owners, deadlines and completion states with the user's own connection.
On this page
Overview
Use OpenClaw to read a selected Asana task from a conversation. Verify that the saved Agent200 server actually returns tools before asking for task data: saving a server definition and making a successful connection are different checks. Restrict the first request to one task you can open in Asana.
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: OpenClaw documentation. For Asana task fields and optional field selection, see Asana’s task-read reference.
- Connector
- Asana
- Works with
- OpenClaw ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page 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.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Asana to OpenClaw
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page. Enable Asana and the read operations needed for this task in your project. Keep credentials out of chats and source control.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.On current OpenClaw versions, stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while the Gateway is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
A successful probe lists capabilities; the task read below is a separate check of Asana access. Restart or reload the appropriate Gateway after configuration.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Authorize Asana and select a task
Complete the Asana authorization link when requested and supply the task ID of a task you can open. Run the read-only test below.
Test your connection
Run one request to check everything is wired up.
Ask
Use Agent200 to read the Asana task I identify and summarize its owner, due date and completion state. Ask for the task ID if missing. Do not create, assign, complete or delete 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.
Get your API key
Create a key in the Agent200 dashboard. It reaches Asana and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Asana to OpenClaw.
Goal: connect Asana to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/asana/framework/openclaw/ 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 OpenClaw'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 OpenClaw: 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 OpenClaw'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: "Use Agent200 to read the Asana task I identify and summarize its owner, due date and completion state. Ask for the task ID if missing. Do not create, assign, complete or delete 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.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/asana/framework/openclaw.md
Asana tools OpenClaw can call
-
Read a task
Readasana_get_taskRetrieve an Asana task's details, including its description, assignee, due date and completion status.
-
Search tasks
Readasana_search_tasksSearch workspace tasks by text and filters. Requires Asana premium search access.
-
List project tasks
Readasana_list_project_tasksList the tasks in a selected project, then read individual tasks for descriptions, ownership and deadlines.
-
List subtasks
Readasana_list_subtasksList the subtasks of a parent task so your agent can inspect the smaller work items behind it.
-
List projects
Readasana_list_projectsList projects in a workspace to find the project relevant to a request.
-
Read a project
Readasana_get_projectRead a project's name and description to understand its purpose and context.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in Asana.
-
02
OpenClaw picks a tool
It sees the Asana tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Asana connection, within the tools and scopes your project allows.
-
04
OpenClaw 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.
FAQ
Why does saving the MCP server not prove Asana works?
Saving records a configuration. A live MCP probe checks discovery; a task read checks the selected tool and the connected Asana account. Complete both checks and inspect the returned task rather than treating a saved configuration as a successful integration.
