A
licenseNot graded
qualityB
maintenanceMCP server for searching and retrieving pages from Atlassian Confluence.
41 npm
1
MIT
Confluence MCP Server
Related Servers
Alternatives to Confluence MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Confluence Cloud/Server/Data Center, enabling page search, CQL queries, page CRUD, attachment upload, and user identity lookup.23392 npm4MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for searching internal Confluence documentation with features like score-based ranking, noun extraction, and LLM query rewriting.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server implementation for interacting with self-hosted Confluence Data Center or Server instances via search, content retrieval, and optional write operations. It features space auto-discovery, audit logging, and granular access control for secure enterprise collaboration.Academic Free v1.1
- AlicenseNot gradedqualityBmaintenanceMCP server for reading Confluence Server/DC documents with search, page content, metadata, spaces, page tree, and attachment/image support.3 npmMIT
- FlicenseAqualityCmaintenanceMCP server for Confluence REST API enabling page retrieval, attachment downloads, space listing, comment access, and full-text search via tools.6-
TDQS
C2.9/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: get_confluence_page retrieves a specific page by ID, while search_confluence performs a broader content search. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on whether it needs a known page or wants to find pages matching a query.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern (get_confluence_page and search_confluence) with snake_case naming. The verbs 'get' and 'search' are appropriate and distinct, and the naming scheme is predictable across the set.
Tool Count2/5
With only 2 tools, this server feels severely under-scoped for a Confluence integration. A typical Confluence server would need tools for creating, updating, deleting pages, managing spaces, and handling attachments, among others. This minimal set limits agents to read-only operations, which is inadequate for most workflows.
Completeness2/5
The tool surface is significantly incomplete for a Confluence domain. It only supports retrieving and searching pages, missing essential CRUD operations (create, update, delete), space management, user operations, and content manipulation. Agents will face dead ends when trying to perform basic tasks like editing or organizing content.
Maintenance
ActivityInactive
ResponsivenessNo issues