AgentDrives
Free check
Asanaasana.com

Can an AI agent use Asana?

As of 6 Oct 2026, an AI agent can't use Asana on its own: reCAPTCHA checkbox on the sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean
Visit Asana Follow changes

Driven 6 Oct 2026Same level in 3 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

  • Agents on a serverTurned away when they send the sign-up form.
  • Signed agentsThe sign-up page opens. The check on the form still applies.
  • Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Asana.

On its own

  • Read Asana's developer documentation in a machine-friendly format
  • See how the sign-up page's security check responds to an automated browser

What it can't, and why

  • Create an Asana accountThe sign-up form shows a visible "I'm not a robot" check after rejecting the automated attempt
  • Get an API key or connect an AI tool to AsanaKeys and tool connections need a signed-in account first, and only the website offers a way to get one
  • Buy a paid plan or use task dependencies, goals, portfolios, or AI featuresBuying starts with the same blocked sign-up, and several features also require a paid plan the agent never reached
Needs a person

Can an AI agent sign up for Asana on its own?

No. Sign-up: needs a human. Web form only (asana.com/create-account). Invisible reCAPTCHA Enterprise rejected our agent's browser: POST app.asana.com/-/signup -> {"recaptcha_invalid":true}, then a visible reCAPTCHA checkbox.

Official server · no call worked

Does Asana have an MCP server, and can an agent connect to it?

Yes. Asana has an official MCP server. The server signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 2 attempts worked.

What the drive found

APIOpenAPIMCP · official–CLIllms.txtWebhooksSandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Asana.

Where agents stop in Asana today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

  1. Let verified agents through sign-upStep-by-step guide
  2. Offer a headless credential pathStep-by-step guide
  3. Support CIMD for MCP client registrationStep-by-step guide
2 more fixes
  1. Publish an MCP server card Step-by-step guide
  2. Retire the beta MCP authorization server Step-by-step guide
  • Claim it free and reply next to the result.
  • A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
  • Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Get a DriveClaim it free
See the example report
Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

Driven · L1 · Needs a person badge

Behind the level.

Our agent couldn't get into Asana, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history · paid plans

Part scores

Agent-ready setup

  • llms.txt
  • OpenAPI
  • MCP server
  • CLI

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

  1. 1 Oct 20262 drivesL1Needs a person
  2. 6 Oct 2026L1Needs a person

Needs a paid plan

Not counted in the level.

CapabilityPlan
Task dependencies / critical pathStarter (Advanced for critical path)
GoalsAdvanced
PortfoliosAdvanced
AI TeammatesStarter+
AI StudioStarter+

For agents and builders.

The drive as data, every checkpoint and all 23 attempts.

How an agent connects · 3 tips

/api/tools/asana.json/tools/asana.mdMCP get_tool {"slug":"asana"}

  • You need a human-created Asana account; then get a PAT at app.asana.com/0/my-apps and call https://app.asana.com/api/1.0 with Authorization: Bearer
  • Use MCP v2 at https://mcp.asana.com/v2/mcp with a pre-registered OAuth client; the beta /sse endpoint is announced as deprecated
  • Read docs as Markdown: append .md or send Accept: text/markdown
Every checkpoint, in detail · 9 checkpoints
  1. DocsHeadlessdevelopers.asana.com/llms.txt and .md pages (Accept: text/markdown -> text/markdown, Vary: Accept); OpenAPI github.com/Asana/openapi declares openapi 3.0.0, 251 operations
  2. Sign upNeeds a humanWeb form only (asana.com/create-account). Invisible reCAPTCHA Enterprise rejected our agent's browser: POST app.asana.com/-/signup -> {"recaptcha_invalid":true}, then a visible reCAPTCHA checkbox.
  3. VerifyNot reachedNot reached: sign-up not completed
  4. KeyNot reachedPAT only from the web developer console (app.asana.com/0/my-apps); OAuth on app.asana.com needs a signed-in user (no device flow, no DCR/CIMD). DCR on the legacy MCP AS returned a client_id, but consent still needs an Asana login.
  5. First callNot reachedGET /api/1.0/users/me -> 401 Not Authorized; no unauthenticated endpoints
  6. First actionNot reachedNo credential
  7. PayNot reachedPurchase now (Starter $10.99/user/month annual) opens the same reCAPTCHA-gated sign-up modal before any checkout; no 402, x402, MPP, UCP or billing API; x402./mpp./agents. subdomains redirect to /404; not in x402 Bazaar or mpp.dev. Checkout itself not reached.
  8. CancelNot reachedNo plan started. Help Center: Admin console > Billing > Plan details > Cancel plan (web UI only); not tested
  9. DeleteNot reachedNo account created. Help Center: Settings > Account > Delete my account (web/mobile UI), deleted within 30 days; no API route found
The attempt log · 23 attempts
CapabilityRouteResultEvidence
MCP discover: POST server/discover (2026-07-28) to https://mcp.asana.com/v2/mcpmcpblocked ✓401 WWW-Authenticate: Bearer realm="Asana MCP", resource_metadata="https://mcp.asana.com/.well-known/oauth-protected-resource/v2", error_description="Authorization header is required for MCP V2 access"
Agent cards / aipref / markdown: probe ai-catalog, agent-card, agent.json, mcp server-card, robots Content-Usage, markdown negotiation, llms.txtapidone ✓asana.com/.well-known/{ai-catalog.json,agent-card.json,agent.json,mcp/server-card.json,ucp} 404 HTML; mcp.asana.com/v2/mcp/server-card 404; robots.txt has no Content-Usage/Content-signal lines; asana.com/llms.txt 200 and developers.asana.com/llms.txt 200; developers.asana.com/docs/using-asanas-mcp-server with Accept: text/markdown -> 200 text/markdown, Vary: Accept; .md URL also 200 text/markdown
Pay step probes: x402./mpp./agents. subdomains, /.well-known/ucp, /auth.md, /SKILL.md, unauthenticated APIapidone ✓x402.asana.com, mpp.asana.com, agents.asana.com -> 307 to asana.com/404; /.well-known/ucp, /auth.md, /SKILL.md 404 HTML; GET app.asana.com/api/1.0/users/me -> 401 JSON Not Authorized, no 402, no payment headers
Find docs: Find API docs, OpenAPI, auth docs, llms.txtapidone ✓developers.asana.com/llms.txt 200 lists guides + reference .md pages; OpenAPI at github.com/Asana/openapi defs/asana_oas.yaml declares openapi: 3.0.0, 251 operationIds; PAT doc says PAT is generated in developer console app.asana.com/0/my-apps (web UI); developer sandbox is a request form with up to 1 week processing
Sign up: Create a free account with the agent's inboxbrowserblocked ✓No documented API/CLI sign-up; web form asana.com/create-account. Invisible reCAPTCHA Enterprise rejected our agent's browser: POST app.asana.com/-/signup -> 200 {"recaptcha_invalid":true}; page then rendered a visible reCAPTCHA "I am not a robot" checkbox (browser/shots/008.png).
Sign up (human handoff): Ask a human to tick the reCAPTCHA checkbox in our agent's browserbrowserblocked ✓
Verify email: Verify sign-up emailnoneblockedno sign-up submitted, so no verification mail
Get API credentials: Create a PAT or OAuth tokenapiblocked ✓PAT is created only in the web developer console app.asana.com/0/my-apps (docs/personal-access-token.md); OAuth AS app.asana.com metadata: authorization_code/refresh_token/jwt-bearer (ID-JAG profile), no device_authorization_endpoint, no registration_endpoint, no CIMD flag; all paths need a signed-in Asana user
MCP client registration: Register an OAuth client via DCR on the legacy MCP ASmcppartial ✓POST https://mcp.asana.com/register -> 201 with client_id (token_endpoint_auth_method none); DELETE registration_client_uri -> 404. The v2 server PRM points to app.asana.com which has no registration_endpoint and no client_id_metadata_document_supported
First API call: GET /users/me without credentialsapiblocked ✓GET https://app.asana.com/api/1.0/users/me -> 401 application/json {"errors":[{"message":"Not Authorized","help":"...https://developers.asana.com/docs/errors"}]} (not problem+json); no public unauthenticated endpoints
Pay step: Find how an agent could buy Starternoneblocked ✓pricing page: Personal $0 Free forever; Starter $10.99/user/month annual, Purchase now -> asana.com/pricing#buy-starter which opens a sign-up modal (JS: buy-starter ModalBody with signup-modal-recaptcha-container); no 402 on API or x402./mpp./agents. subdomains (307 to /404); no /.well-known/ucp; developers llms.txt has 0 mentions of billing/x402/402/checkout; not listed in x402 Bazaar or mpp.dev services
Cancel plan: Cancel plannoneskippedno plan started; help.asana.com/s/article/how-to-cancel-your-asana-plan (via web search): Admin console > Billing > Plan details > Cancel plan (web UI)
Delete account: Delete accountnoneskippedno account created; help.asana.com/s/article/delete-your-asana-account (via web search): Settings > Account > Delete my account (web/mobile UI), deletion within 30 days; no API route found in developers llms.txt
Create and manage tasks (assignee, due date, description, subtasks): drive on free planapiblockedAPI returns 401 without a token
Create and organize projects: drive on free planapiblockedAPI returns 401 without a token
View work in List, Board, Calendar, Timeline/Gantt views: drive on free planapiblockedAPI returns 401 without a token
Comment and collaborate on tasks (Stories): drive on free planapiblockedAPI returns 401 without a token
Mark tasks complete / track status: drive on free planapiblockedAPI returns 401 without a token
Set task dependencies and critical path: driveapiplan_gatedasana.com/pricing lists this under a paid tier (Starter: Timeline/Gantt + dependencies, AI Teammates/AI Studio requests and credits; Advanced: Portfolios, Goals); also no account to try
Set and track Goals (company/team/individual, weighted, progress): driveapiplan_gatedasana.com/pricing lists this under a paid tier (Starter: Timeline/Gantt + dependencies, AI Teammates/AI Studio requests and credits; Advanced: Portfolios, Goals); also no account to try
Group projects into Portfolios with health/status reporting: driveapiplan_gatedasana.com/pricing lists this under a paid tier (Starter: Timeline/Gantt + dependencies, AI Teammates/AI Studio requests and credits; Advanced: Portfolios, Goals); also no account to try
Delegate work to an AI Teammate (prebuilt agent persona, e.g. Project Manager, Launch Coordinator): driveapiplan_gatedasana.com/pricing lists this under a paid tier (Starter: Timeline/Gantt + dependencies, AI Teammates/AI Studio requests and credits; Advanced: Portfolios, Goals); also no account to try
Build custom agentic workflows with AI Studio (drag-and-drop automation + AI steps): driveapiplan_gatedasana.com/pricing lists this under a paid tier (Starter: Timeline/Gantt + dependencies, AI Teammates/AI Studio requests and credits; Advanced: Portfolios, Goals); also no account to try

Also in Project management.

All of Project management, by level