confluence-mcp
Related Servers
Alternatives to confluence-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server for integrating Confluence with AI applications, enabling listing spaces, browsing and searching pages, and retrieving Confluence instance info.-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that connects AI agents to Confluence Cloud. Agents can search, read, create, and update Confluence content — pages, comments, links, images, and labels.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to read Confluence page content by URL, supporting self-hosted Confluence with basic auth.-
- AlicenseBqualityDmaintenanceAn MCP server that connects AI assistants to Confluence, enabling search and fetch of pages in real time.22MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to interact with Atlassian products (Confluence and Jira) for content management, issue tracking, and project management through a standardized interface.2,658 npm6MIT
- AlicenseAqualityCmaintenanceMCP server for Confluence Server/Data Center (self-hosted) that gives LLM agents access to search, read, create/edit pages, comments, labels, and attachments via the Confluence REST API.1526 npmISC
TDQS
Scored across 7 tools
Each tool targets a distinct operation: retrieval by ID, by title, listing space pages, listing children, search, importing from Confluence, and exporting to Confluence. There is no meaningful overlap, and the descriptions make the boundaries clear.
All tool names use snake_case and follow a clear pattern: get_* for retrieval operations, search_* for querying, sync_* and push_* for transfer operations. The naming is consistent and predictable.
With 7 tools, the server is well-scoped. Each tool serves a necessary function for reading, searching, and syncing Confluence content, without unnecessary bloat or redundancy.
The tool set covers the primary lifecycle for Confluence content: read (by id, title, space, children, search) and write/update via push_md_to_confluence. The main gap is lack of a direct delete or page management operation, but the core workflows are well supported.