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.1529 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,965MIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.MIT
- AlicenseNot gradedqualityDmaintenanceProduction-ready MCP server for Atlassian Jira and Confluence, providing tools for issue management, page retrieval, and content operations.60 npm1MIT
TDQS
A3.9/5.0
Scored across 162 tools
Disambiguation4/5
Despite 162 tools spanning many domains, descriptions are unusually careful about boundaries — e.g. jira_edit vs jira_write, git_check_commits vs git_lint_commits, datadog_monitor_list vs datadog_monitor_search, and drive_docs_read vs drive_file_read each explicitly cross-reference and distinguish themselves. A few pairs remain close (jira_comment vs jira_comment_edit vs jira_comment_delete; confluence_comment_* cluster) and long descriptions risk being skimmed, but misselection is unlikely.
Naming Consistency5/5
Tool names are uniformly snake_case with a consistent service_resource_action pattern (confluence_comment_reanchor, jira_sprint_create, datadog_monitor_get, drive_sheets_append). Prefixes cleanly partition domains, and even the oddballs (jev_route, ai_chat, log_search) fit the convention.
Tool Count2/5
162 tools is far past any reasonable single-surface count and will strain an agent's selection ability; the JIRA surface alone is ~60 tools, and the Confluence comment family alone is 11. Many are microscopic single-purpose wrappers (confluence_label_add, confluence_watcher_status, datadog_downtime_list) that would be better as actions on a few tools.
Completeness5/5
Coverage is exhaustive: full CRUD+lifecycle on JIRA issues, sprints, versions, components, worklogs; Confluence pages, comments, restrictions, attachments, watchers; Datadog list/get across every major resource; Drive read/write/search/lease; Gmail read/search/drafts; git commit analysis; Snowflake queries. Explicit dry_run, confirm-gated deletes, and account-discovery tools eliminate the usual dead ends.
Maintenance
ActivityActive
ResponsivenessSyncing