A
licenseA
qualityB
maintenanceEnables querying and managing Jira issues and Confluence pages through their Cloud REST APIs, preserving markdown formatting via direct ADF conversion.
16
MIT
atlas-lite-mcp
Related Servers
Alternatives to atlas-lite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with multiple Jira and Confluence workspaces simultaneously, with automatic account routing by URL or issue key.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to search, read, and manage Confluence Cloud pages, including publishing and updating documentation from Markdown, with support for folders and secure API token storage.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible editors to connect to Jira Cloud with a user-supplied API token, verify the connection, and fetch issue details through natural-language requests.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and other MCP clients to run live JQL and CQL searches and read Jira Cloud issues, comments, and Confluence Cloud pages on your own machine, with no local index and nothing cached outside those products. Access is read-only and scoped to your own Atlassian account permissions.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read Confluence Cloud pages as markdown, browse page trees, download image attachments, and diff content against local documentation.MIT
TDQS
B3.2/5.0
Scored across 19 tools
Disambiguation4/5
Each tool targets a clear resource+action pair, and the three page-mutation variants (page_edit for find/replace, page_update_section for heading-scoped replacement, page_append for end-of-page) are distinguished by explicit descriptions. Minor residual overlap between page_edit and page_update_section could still cause misselection in edge cases, and page_get vs table_get requires the agent to know whether it needs a table specifically.
Naming Consistency4/5
Names follow a predictable resource_action pattern (page_get, table_update, issue_create, issue_transition) grouped by domain prefix. Small deviations exist: sites_list is plural where others are singular, and multi-word actions like page_update_section and table_add_row break the two-token rhythm slightly, but the convention remains readable.
Tool Count4/5
19 tools serve two distinct product surfaces (Confluence pages/tables and Jira issues), so the count is roughly proportional to scope and each tool maps to a real operation. It sits near the upper end of comfortable, with the page-editing family being the only area that feels finer-grained than strictly necessary.
Completeness4/5
Both domains have near-full lifecycle coverage: pages support create/read/edit/append/delete/search/comment and issues support get/search/create/update/delete/transition/comment. Gaps are minor but present — no table row deletion or table creation, no page label or attachment operations, and no way to restore a trashed page.
Maintenance
ActivityMaintained
ResponsivenessNo issues