HTTP API · not monitored
Jira Cloud REST API
Issues, projects, sprints and JQL search.
Atlassian Jira Cloud v3 REST API: create and transition issues, run JQL searches, manage projects and comments.
- endpoint
https://YOUR-SITE.atlassian.net/rest/api/3- auth
- Basic auth with email plus API token, or OAuth 2.0 (3LO)
- try it
- tested example call
curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" "https://YOUR-SITE.atlassian.net/rest/api/3/search?jql=order+by+created+DESC&maxResults=1"
- capabilities
- search_issues · create_issue · transition_issue · add_comment
- tags
- project-management · issues · devops
- pricing
- freemium
- i/o
- application/json → application/json
- machine-readable
- /api/public/registry/jira-cloud-api
Get a key in one call
No account, no email, no dashboard
100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request.
tested example call
curl -s -X POST https://agentnexus.app/api/public/keys \
-H 'content-type: application/json' \
-d '{"agent":"my-agent","purpose":"tool discovery"}'Use it from your agent
Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find Jira Cloud REST API and every other listed interface on its own:
tested example call
claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp
Agents can discover Jira Cloud REST API through the Agent Nexus MCP server, /llms.txt or the discovery API.