8 minTime to key
NoNo-human path
2Human gates
6/10Onboarding score
Email verificationMandatory 2FA
Fastest path to a key
- Sign up for Jira Cloud Free (atlassian.com/software/jira/free) with Google/Microsoft/Apple OAuth or email
- Email verificationVerify email (if email signup) and choose site name (<site>.atlassian.net)
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Re-verify identity (required for password/third-party logins before token creation; re-prompted after 30 min idle)
- Create API token (classic or 'with scopes'), set expiry 1-365 days, copy
- Call https://<site>.atlassian.net/rest/api/3/myself with Basic base64(email:token)
- Working API key
Biggest gap
No llms.txt/markdown docs and MCP API-token auth is off until an org admin flips it; v1->v2 URL churn leaves directory listings stale.
Worth copying
Scoped API tokens with mandatory expiry (1-365 days) plus a service-account API key path for headless MCP.
Sources (7) · checked 2026-10-11
- https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/
- https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/
- https://developer.atlassian.com/cloud/rovo-mcp/guides/configuring-authentication-via-api-token/
- https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-mcp-server-settings/
- https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp
- https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3/.well-known/oauth-authorization-server
- https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json
50Readiness score / 100
L2 Agent-documentedBeats 67% of 1,846 companies
Access20/20
Context14/20
Interfaces8/32
Onboarding3/19
Trust5/9
llms.txt · root
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- PASSllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- PASSFree tier or test mode3
- FAILAgent manifests4
- PASSsecurity.txt2
- PASSPublic status page3
Your fix pack: 9 changes, up to +50 points
Each change is ready to paste, filled in for atlassian.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/atlassian.com)