A
licenseA
qualityC
maintenanceAn MCP server for reading and writing Confluence pages in native Atlassian Document Format (ADF), enabling precise edits at the document node level without loss of formatting.
43
MIT
omni-dev
by rust-works
Related Servers
Alternatives to omni-dev
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to Jira and Confluence, enabling search, create, update, and comment operations with rich Markdown-to-ADF conversion.1525 npm2MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for bidirectional Markdown-to-Confluence sync, enabling download and publish of Confluence pages as Markdown with images, frontmatter tracking, and dry-run safety.-
- AlicenseNot gradedqualityAmaintenanceModel Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.5,890MIT
- AlicenseNot gradedqualityBmaintenanceModel Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.MIT
- AlicenseNot gradedqualityCmaintenanceProduction-ready MCP server for Atlassian Jira and Confluence, providing tools for issue management, page retrieval, and content operations.26 npm1MIT
TDQS
A3.7/5.0
Scored across 148 tools
Disambiguation4/5
The domain-prefixed names (jira_, confluence_, datadog_, etc.) make most tools clearly distinct, and descriptions are thorough about cross-references. A few pairs overlap functionally — jira_edit vs jira_write both update an issue, and git_check_commits vs git_lint_commits both validate commit messages — but the descriptions draw usable lines. Overall an agent can usually tell tools apart.
Naming Consistency4/5
The dominant pattern is domain_resource_verb (confluence_attachment_upload, datadog_monitor_list, jira_sprint_create), which is highly predictable. Deviations exist: git tools mix verb forms (git_create_pr, git_twiddle_commits, git_branch_info) and a handful of tools drop the resource noun (jira_create, ai_chat, log_search). Still, the convention is consistent enough to infer behavior.
Tool Count2/5
148 tools exceeds any reasonable well-scoped range; even for a multi-service wrapper this is a heavy selection burden. Some consolidation is possible (e.g., jira_transition_list duplicates jira_transition's list mode) and the count makes the server hard to navigate. The breadth of integrated services justifies a large set, but not this large.
Completeness4/5
Each major domain has strong lifecycle coverage: JIRA spans issues, comments, attachments, labels, links, versions, sprints, worklogs, and watchers; Confluence covers pages, comments, attachments, labels, and restrictions. Minor documented gaps remain — Gmail has no send or label-mutation tool, and Datadog is read-only — but agents can work around them via the CLI. No critical dead ends in the core workflows.
Maintenance
ActivityActive
ResponsivenessSyncing