{"id":"ankitranjan5-atlassian-mcp-server","name":"atlassian-mcp-server","af_score":53.5,"security_score":67.0,"reliability_score":17.5,"what_it_does":"Provides a Spring Boot MCP (SSE-based) server that performs Atlassian OAuth2 (Jira + Confluence Cloud), stores encrypted tokens in a database, refreshes tokens automatically, and exposes MCP “tools” for Jira issue operations and Confluence page/space operations.","best_when":"You can run a local or private Spring Boot service, complete Atlassian OAuth consent for the target user, and then let an agent call the exposed MCP tools using the connection token.","avoid_when":"You need turnkey hosted SaaS reliability/SLA, or you can’t securely manage encryption passwords, database credentials, and per-user access tokens.","last_evaluated":"2026-04-04T20:01:55.296082+00:00","has_mcp":true,"has_api":false,"auth_methods":["OAuth2 authorization_code (Atlassian)","Bearer Authorization header using an Atlassian connection token (principalName/UUID) for MCP tool calls"],"has_free_tier":false,"known_gotchas":["OAuth scopes must be correctly configured for Jira/Confluence; 401s may indicate missing/incorrect scopes","The agent must use the connection token (principalName/UUID) produced after OAuth success; expired/incorrect tokens will fail tool calls","The README references enabling logs for debugging raw Confluence HTTP responses; agents may need log visibility for troubleshooting","MCP transport is SSE; ensure the agent/client supports SSE and that endpoint access (including headers like Authorization) is configured correctly"],"error_quality":0.0}