Asana + Hermes Agent
How to connect Asana to Hermes Agent
Use Hermes Agent 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 Hermes Agent to inspect a selected Asana task from your own machine or server. Check the Agent200 MCP tool list after configuring the server, then run one read before building a wider project briefing. Use the discovered schemas when calling tools.
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: Hermes Agent documentation. For Asana task fields and optional field selection, see Asana’s task-read reference.
- Connector
- Asana
- Works with
- Hermes Agent ยท 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.
- Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.
Connect Asana to Hermes Agent
-
1
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 Hermes Agent 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.
-
2
Step 2: Store your key in ~/.hermes/.env
Keep the key out of
config.yaml: Hermes reads it from~/.hermes/.env.~/.hermes/.envMCP: Hermes Agent key in ~/.hermes/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Add the server to ~/.hermes/config.yaml
Add an entry under
mcp_serverswith the URL and the Authorization header. Do not settransport: sse: Agent200 serves streamable HTTP.~/.hermes/config.yamlMCP: Hermes Agent config.yaml entry mcp_servers: agent200: url: "https://api.agent200.com/mcp/" headers: Authorization: "Bearer ${AGENT200_API_KEY}" -
4
Step 4: Reload and test
In a running session, run
/reload-mcp, or restart Hermes. Then check what the server returned from a terminal.TerminalMCP: Hermes Agent reload and test # In a running Hermes session: /reload-mcp hermes mcp test agent200 hermes mcp list -
5
Step 5: Connect your Asana account
The first time you ask Hermes Agent 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 Hermes Agent or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Use the Agent200 MCP tools to read the Asana task I identify. Report its owner, due date and completion state, and identify any unavailable fields. Ask for the task ID if absent. Do not modify Asana.
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 Hermes Agent.
Goal: connect Asana to Hermes Agent with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/asana/framework/hermes-agent/ 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 Hermes Agent'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 Hermes Agent: 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 Hermes Agent'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 the Agent200 MCP tools to read the Asana task I identify. Report its owner, due date and completion state, and identify any unavailable fields. Ask for the task ID if absent. Do not modify Asana." 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/hermes-agent.md
Asana tools Hermes Agent 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 Hermes Agent
In your own words, for something in Asana.
-
02
Hermes Agent 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
Hermes Agent 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
Which tool name should Hermes call?
Use the name advertised by your Hermes MCP connection. Hermes may expose a server-prefixed name; the Asana catalogue identifies the underlying operation. Do not construct argument names or assume a prefixed name without checking the discovered definition.

