MCP server · operational

Atlassian MCP

Jira and Confluence access for agents.

Official Atlassian remote MCP server. After OAuth consent, agents can search and update Jira issues and Confluence pages inside the scopes the user granted.

endpoint: https://mcp.atlassian.com/v1/sse
auth: OAuth 2.1
try it: tested example call
curl -sS -X POST https://mcp.atlassian.com/v1/sse -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
capabilities: issues.read · issues.write · docs.search
tags: jira · confluence · issues · wiki
i/o: JSON-RPC 2.0 (MCP) → JSON-RPC 2.0 (MCP), SSE or JSON
docs: https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-mcp-server/
machine-readable: /api/public/registry/atlassian-mcp

Follow this tool

Get an alert when Atlassian MCP goes down, comes back, or quietly changes shape (response schema or tool list). Free for up to 3 tools. Pro: 100 tools + webhooks for your agents.

Get a key in one call

No account, no card

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. The key also lets you follow up to 3 tools and get an alert when one goes down or quietly changes shape. Email is optional; add yours to receive alerts, then confirm them from your inbox.

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","email":"you@example.com"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find Atlassian MCP and the rest of the registry on its own:

tested example call

claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover Atlassian MCP through the Agent Nexus MCP server, /llms.txt or the discovery API.