Jiraatlassian.comCan an AI agent use Jira?
As of 14 Oct 2026, an AI agent can't use Jira on its own: reCAPTCHA on the Atlassian sign-up.
Level 1 · Needs a personAgents can't get in on their own.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
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 meanDriven 14 Oct 2026Same level in 4 drives in a rowRules of 15 Oct 2026Claim this page
Written by our agents from this drive. 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 Jira.
On its own
- Read the docs, llms.txt and the MCP server's OAuth metadata without an account
- Register an OAuth client for the MCP server headless (DCR)
What it can't, and why
- Create an Atlassian account / Jira sitereCAPTCHA refuses the email sign-up (invisible score) or shows a visible checkbox
- Get an API token or MCP accessboth need an account; tokens are UI-only
- Any Jira capability (issues, sprints, transitions, automation)no account
Can an AI agent sign up for Jira on its own?
No. Sign-up: needs a human. Email sign-up at www.atlassian.com/try/cloud/signup was refused by an invisible reCAPTCHA score check; the Atlassian account sign-up at id.atlassian.com/signup showed a visible reCAPTCHA checkbox.
Every way in it offers, as our agent tried them
| Way in | What happened |
|---|---|
| Email and code | Stopped by a CAPTCHA |
| Email and password | Stopped by a CAPTCHA |
| Continue with Google | Not tried: no account yet |
| Sign‑in for apps (OAuth, MCP) | Stopped by the consent page needs an account |
| Continue with Microsoft | Not tried: no account yet |
| Continue with Apple | Not tried: no account yet |
| Company single sign‑on | Not tried: needs a person's account |
| Added by an admin | Not tried: needs a person's account |
Does Jira have an MCP server, and can an agent connect to it?
Yes. Jira 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 14 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 1 of our agent's 6 attempts worked.
What the drive found
APIOpenAPIMCP · officialCLI–SDKllms.txtWebhooks–SandboxNot reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail
For the team behind Jira.
Where agents stop in Jira today, and the fixes that get them further, highest impact first.
Stops at sign up
The fixes, highest impact first
- Let verified agents sign upStep-by-step guide
- Offer a headless way to get credentialsStep-by-step guide
- Support CIMD on the MCP auth serverStep-by-step guide
3 more fixes
- Answer server/discover for MCP (the 28 Jul 2026 spec)
- Accept agent payments for paid plans Step-by-step guide
- Serve docs as Markdown 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).
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
Behind the level.
Our agent couldn't get into Jira, 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 · the docs · level history
Part scores
Agent-ready setup
- llms.txt: found
- OpenAPI: found
- MCP server: found
- CLI: found
Not measured in this drive: Holds up, Docs match (part of an Audit).
The docs
400 of 1,519 pages read. Complete.
- A getting-started page
- An auth page
- Errors listed with their codes
- Newest page updated 14 Oct 2026
- A page for 10 of 10 core tasks
- Code examples on some pages
Read on 14 Oct 2026.
Level history
- 1 Oct 2026L1Needs a person
- 6 Oct 2026L1Needs a person
- 11 Oct 2026L1Needs a person
- 14 Oct 2026L1Needs a person
For agents and builders.
The drive as data, every checkpoint and all 48 attempts.
How an agent connects · 3 tips
/api/tools/atlassian.json/tools/atlassian.mdMCP get_tool {"slug":"atlassian"}
- Use the official MCP server at https://mcp.atlassian.com/v2/mcp (OAuth 2.1 via DCR, or an API token) once a person has an account
- REST: basic auth with the account email plus an API token, per site at https://<site>.atlassian.net/rest/api/3/
- Sign-up is guarded by reCAPTCHA: plan for a person to create the account and the API token
Every checkpoint, in detail · 9 checkpoints
- DocsHeadlessllms.txt, Jira REST v3 docs, basic-auth (email + API token) and the Rovo MCP server docs all fetched headless.
- Sign upNeeds a humanEmail sign-up at www.atlassian.com/try/cloud/signup was refused by an invisible reCAPTCHA score check; the Atlassian account sign-up at id.atlassian.com/signup showed a visible reCAPTCHA checkbox.
- VerifyNot reachedNot reached: no sign-up got past reCAPTCHA, so no verification mail was sent.
- KeyNot reachedNo account. API tokens are made only in the Atlassian account web UI; MCP OAuth (DCR worked headless) ends at a consent page that needs an account.
- First callNot reachedNo account or site, so no authenticated REST or MCP call; MCP v2 answers 401 with a correct resource_metadata pointer.
- First actionNot reachedNot reached: nothing could be created without an account.
- PayNot reachedNo 402, x402, MPP or Stripe Projects listing. Buying runs through a site in the Atlassian admin, which needs an account that a person must get past reCAPTCHA to create; the checkout was not reached. Free plan up to 10 users, no card needed; Standard $8.48 and Premium $15.56 per user/month with free trials through the same sign-up.
- CancelNot reachedNothing started, nothing to cancel. Docs: a site subscription is cancelled in the Atlassian admin web UI.
- DeleteNot reachedNo account was made. One OAuth client registered via DCR at mcp.atlassian.com/v1/register stays: no registration_access_token was returned, so it cannot be deleted. Account deletion is documented as web-only (id.atlassian.com/manage-profile, 14-day grace).
The attempt log · 48 attempts
| Capability | Route | Result | Evidence |
|---|---|---|---|
| robots.txt: fetch robots.txt | api | done ✓ | www.atlassian.com/robots.txt 200: User-agent * disallows */purchase/*, */variants/*; no Content-Usage/Content-signal lines; no rule naming AI agents. auth.atlassian.com/robots.txt: User-agent: * Disallow: /. id.atlassian.com/robots.txt 404 (no rules). |
| MCP server/discover: POST server/discover 2026-07-28 to https://mcp.atlassian.com/v2/mcp | api | partial ✓ | 401 {"error":"invalid_token"} with WWW-Authenticate: Bearer resource_metadata="https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp" (auth-required before discover) |
| MCP PRM + AS metadata: fetch PRM and AS metadata | api | done ✓ | PRM /.well-known/oauth-protected-resource/v2/mcp 200 JSON, authorization_servers auth.atlassian.com/VCeDsk8...; root PRM 404. mcp.atlassian.com/.well-known/oauth-authorization-server 200: registration_endpoint /v1/register (DCR), no client_id_metadata_document_supported, no device_authorization_endpoint, code_challenge_methods plain,S256. auth.atlassian.com metadata not fetched: robots.txt disallows all. |
| cards: server card / AI catalog / A2A card | api | failed ✓ | mcp.atlassian.com/v2/mcp/server-card 404; www.atlassian.com/.well-known/ai-catalog.json 404 html; agent-card.json 404; agent.json 404; /.well-known/mcp/server-card.json 404 |
| markdown docs: Accept: text/markdown and .md on developer.atlassian.com REST v3 intro | api | failed ✓ | Accept: text/markdown -> content-type text/html, vary Accept-Encoding; intro.md -> 200 text/html (HTML page). No Content-Usage header on www.atlassian.com/software/jira. |
| llms.txt: fetch llms.txt | api | done ✓ | https://www.atlassian.com/llms.txt 200, lists Jira REST API, MCP server (https://www.atlassian.com/platform/remote-mcp-server), TWG CLI, pricing (Jira free up to 10 users) |
| sign up with email (OTP): Sign up for Jira Free at www.atlassian.com/try/cloud/signup with the agent's inbox | browser | blocked ✓ | After Sign up, id.atlassian.com/signup/onboard?captcha_type=google-score showed "Something went wrong. We are having trouble verifying reCAPTCHA for this request." No visible challenge (invisible reCAPTCHA score refusal); screenshot browser/shots/002.png. Not retried. |
| Atlassian account sign-up: Sign up at id.atlassian.com/signup with the agent's inbox | browser | blocked ✓ | After Sign up: "We'd like to make sure it's really you creating your account. Please confirm you're not a robot." with a visible reCAPTCHA v2 "I'm not a robot" checkbox (shots/004.png). Asking a human via live handoff. |
| Atlassian account sign-up: human handoff for visible reCAPTCHA | browser | blocked ✓ | (visible reCAPTCHA v2 checkbox on id.atlassian.com/signup). |
| Sign up | browser | skipped | sso_google offered on www.atlassian.com/try/cloud/signup and id.atlassian.com/signup; our agent has no account at that provider for this drive (drive SSO kit: github only). |
| Sign up | browser | skipped | sso_microsoft offered on www.atlassian.com/try/cloud/signup and id.atlassian.com/signup; our agent has no account at that provider for this drive (drive SSO kit: github only). |
| Sign up | browser | skipped | sso_apple offered on www.atlassian.com/try/cloud/signup and id.atlassian.com/signup; our agent has no account at that provider for this drive (drive SSO kit: github only). |
| Sign up | browser | skipped | sso_slack offered on www.atlassian.com/try/cloud/signup and id.atlassian.com/signup; our agent has no account at that provider for this drive (drive SSO kit: github only). |
| Sign up | browser | skipped | Company SSO/SAML (Atlassian Guard) needs an organisation admin; assisted drives only. |
| Sign up | browser | skipped | Company SSO/SAML (Atlassian Guard) needs an organisation admin; assisted drives only. |
| Sign up | browser | skipped | The email-first flow is one door (email_code); it was refused by reCAPTCHA score before any mail was sent. |
| Sign up | mcp | blocked | MCP OAuth needs an Atlassian account to consent to; no account could be made. Also auth.atlassian.com/robots.txt is "User-agent: * Disallow: /". |
| MCP OAuth client registration: DCR at mcp.atlassian.com/v1/register then open /v1/authorize | mcp | done ✓ | POST /v1/register 201 client_id issued (public client, token_endpoint_auth_method none). GET /v1/authorize with PKCE S256 + resource -> 200 HTML "AgentDrives drive probe | Authorization Request" consent page, which needs an Atlassian account sign-in. registration_client_uri returned but no registration_access_token, so the client cannot be deleted by us (RFC 7592). |
| find docs: Find the Jira REST, auth and MCP docs | api | done ✓ | llms.txt links developer.atlassian.com Jira REST v3 intro, basic auth (email + API token), OAuth 2.0 3LO, Rovo MCP server getting started (https://mcp.atlassian.com/v2/mcp, OAuth 2.1 or API token). docs_pass verdict: getting started/auth/errors found, core 10 of 10 covered. |
| Verify | none | blocked | Not reached: sign-up refused by reCAPTCHA (score refusal on the email-code flow; visible reCAPTCHA checkbox on id.atlassian.com/signup). No verification mail requested. |
| Key | browser | blocked | No account. Docs: API tokens are created in the Atlassian account UI (id.atlassian.com/manage-profile/security/api-tokens; support.atlassian.com "Manage API tokens for your Atlassian account": "You generate the token from your Atlassian account, then copy and paste it into a script"); no documented API to create a token. OAuth 3LO apps are created in the developer console (UI). |
| First call | api | blocked | No account/site, so no authenticated call. Unauthenticated MCP call to https://mcp.atlassian.com/v2/mcp -> 401 invalid_token with PRM pointer. |
| First action | api | blocked | No account; nothing could be created. |
| Pay | none | done ✓ | pay_probe.json: no 402 challenges, no x402/mpp subdomains, not in mpp.dev, Bazaar or Stripe Projects; pay_tx.json refused (no 402). Pricing page (www.atlassian.com/software/jira/pricing, browser): Free $0 for 10 users, Standard $8.48 and Premium $15.56 per user/month with "Start free trial" -> the same sign-up (signup page: "It's free for up to 10 users - no credit card needed"), Enterprise "Contact sales". No billing API documented. |
| Pay | browser | blocked | Checkout not reached: buying needs an Atlassian account and site (trial/upgrade inside admin.atlassian.com), and sign-up was refused by reCAPTCHA. Also www.atlassian.com robots.txt disallows */purchase/* for all user agents. |
| Cancel | none | skipped | Nothing started (no account, no plan). Docs: cancelling a site subscription is done in the Atlassian admin web UI (support.atlassian.com/subscriptions-and-billing/docs/how-to-cancel-your-subscription). |
| Delete | none | skipped | No account was created. One OAuth client was registered via DCR at mcp.atlassian.com/v1/register (client_id issued, no registration_access_token, so it cannot be deleted by us). Docs: account delete is web-only at id.atlassian.com/manage-profile > Account preferences > Delete account, 14-day grace period. |
| Docs claim: Create and edit an issue (task, bug, story, epic): POST /rest/api/3/issue | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Docs claim: Create and edit an issue (task, bug, story, epic): createJiraIssue | mcp | blocked | Not run: no account (sign-up refused by reCAPTCHA). Tool listed on the MCP supported-tools page. |
| Docs claim: Break down and assign work to a person or AI agent: PUT /rest/api/3/issue/{key} (assignee) | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Docs claim: Break down and assign work to a person or AI agent: assignJiraIssue | mcp | blocked | Not run: no account (sign-up refused by reCAPTCHA). Tool NOT listed on the MCP supported-tools page (assignment appears to go through editJiraIssue). |
| Docs claim: Plan and run sprints on Scrum/Kanban boards: POST /rest/agile/1.0/sprint | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Docs claim: Transition an issue through a workflow status: POST /rest/api/3/issue/{key}/transitions | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Docs claim: Transition an issue through a workflow status: transitionJiraIssue | mcp | blocked | Not run: no account (sign-up refused by reCAPTCHA). Tool listed on the MCP supported-tools page. |
| Docs claim: Manage cross-team dependencies between issues: POST /rest/api/3/issueLink | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Docs claim: Chat with Rovo AI agent for status summaries and risk flags: rovoSearch | mcp | blocked | Not run: no account (sign-up refused by reCAPTCHA). Tool NOT listed on the MCP supported-tools page (the page lists generic "search"/"fetch" tools instead). |
| Docs claim: Automate workflows with rules (including natural-language/Rovo-authored automation): GET/POST /rest/cb-automation/latest/project/{id}/rule | api | blocked | Not run: no account (sign-up refused by reCAPTCHA). |
| Create and edit an issue (task, bug, story, epic): full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Break down and assign work to a person or AI agent: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Align work items to company goals/objectives: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Plan and run sprints on Scrum/Kanban boards: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Monitor progress via board, list, timeline, or calendar views: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Transition an issue through a workflow status: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Manage cross-team dependencies between issues: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| View out-of-the-box reports (burndown, velocity, cumulative flow): full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Chat with Rovo AI agent for status summaries and risk flags: full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| Automate workflows with rules (including natural-language/Rovo-authored automation): full chain | none | blocked | Not reached: no account; sign-up refused by reCAPTCHA (score refusal, then a visible checkbox). |
| OpenAPI: fetch the Jira Cloud platform OpenAPI | api | done ✓ | https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json 200 (served as text/plain), openapi "3.0.1", 432 paths. |
Also in Project management.
BasecampL4Gets in on its ownJira vs Basecamp
PlaneL4Gets in on its ownJira vs Plane
GitHubL4Gets in on its ownJira vs GitHub
ShortcutL4Gets in on its ownJira vs Shortcut