confluence-mcp
Related Servers
Alternatives to confluence-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Atlassian Confluence and Jira, supporting both Cloud and Server/Data Center deployments with tools for searching, creating, and updating issues and pages.MIT
- AlicenseNot gradedqualityCmaintenanceProvides JIRA issue search, retrieval, and update functionalities via MCP.71 npmMIT
- FlicenseAqualityAmaintenanceProvides MCP tools to search, create, update, and comment on Jira issues, and to search, create, update, and list Confluence pages and spaces via REST API, including linking Jira issues to relevant Confluence documentation.131-
- FlicenseAqualityDmaintenanceMCP server for JIRA Cloud REST API v3, enabling issue search, creation, updates, comments, and transitions.9-
- AlicenseAqualityCmaintenanceAn MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.12627 npm13MIT
- FlicenseNot gradedqualityBmaintenanceEnables to interact with JIRA issues and sprints through MCP tools, including fetching tickets, adding comments, linking issues, and more.320 npm1-
TDQS
Scored across 13 tools
Each tool targets a distinct operation and domain, with clear separation between Confluence page management and Jira issue tracking. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like create, get, update, execute, and transition appropriately paired with nouns like page, jira_issue, cql_search, etc.
With 13 tools covering both Confluence and Jira operations, the count is well-scoped and balanced—each tool serves a distinct purpose without being overwhelming or insufficient.
The tool set covers essential CRUD operations for both Confluence pages and Jira issues, along with context-specific searches. Missing delete operations and some Jira board management are minor gaps, but core workflows are supported.