[ MCP SERVER SUMMARY ]
Asana MCP server summary
Asana's MCP V2 server exposes the Work Graph to AI assistants — tasks, projects, sections, and status updates over Streamable HTTP. Bifrost connects with OAuth so work-management tools inherit workspace app controls and gateway audit logs.
| Property | Details |
|---|---|
| Company | Asana |
| Connection type | HTTP |
| Authentication | OAuth 2.0 |
| Package or endpoint | https://mcp.asana.com/v2/mcp |
| Capabilities | Tasks and projects, Sections and assignments, Status and reporting queries |
| Official documentation | Asana MCP documentation |
Before you start
- Asana workspace where the MCP client app is allowed
- OAuth client credentials if your host requires them
What you can do with Asana
- Create and triage tasks from Cursor without installing Asana locally
- Respect Asana app management allow/block lists via OAuth apps
- Separate PM vs engineering tool allowlists with virtual keys
[ HOW TO CONNECT ]
Connect Asana to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Asana in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• V2 endpoint: https://mcp.asana.com/v2/mcp (Streamable HTTP).
• Ensure the MCP client app is not blocked in Asana app management.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Asana.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Asana via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "asana",
"connection_type": "http",
"connection_string": "https://mcp.asana.com/v2/mcp",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Asana through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Asana MCP server do?
Asana exposes tasks and projects, sections and assignments, status and reporting queries to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Asana authenticate when used with Bifrost?
Asana uses OAuth 2.0. Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Asana through Bifrost?
Yes. After registering Asana in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Slack
Slack’s MCP server gives AI agents secure access to workplace conversations, channels, and collaboration context.
Intercom
Connect AI assistants to Intercom customer support data and workflows through Intercom’s MCP integration.
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.