Confluence MCP Server
Related Servers
Alternatives to Confluence MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenance🚀 Token-efficient MCP server for Confluence. Reduces LLM costs by 76% via Markdown conversion. Supports listing, searching, and fetching pages.33MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read Confluence Cloud pages as markdown, browse page trees, download image attachments, and diff content against local documentation.MIT
- AlicenseBqualityDmaintenanceEnables querying and interacting with a Markdown wiki generated from Confluence pages, with search and MCP server for LLM access.104MIT
- AlicenseBqualityAmaintenanceEnables Claude Desktop to search, read, and update Confluence Cloud pages, spaces, attachments, comments, and version history through the Confluence REST API v1 and v2 using local stdio.33MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables AI assistants like Claude to access and search Atlassian Confluence content, allowing integration with your organization's knowledge base.54,015 npm61ISC
- FlicenseAqualityDmaintenanceEnables reading and analyzing Confluence documentation content through the Confluence REST API. Supports extracting and converting text, tables, code blocks, and images from Confluence pages for Q\&A and analysis.6-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_space_content retrieves all pages in a workspace, read_page fetches specific page content, and search_confluence performs general searches. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern (list_space_content, read_page, search_confluence) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.
With only 3 tools, the set feels thin for a Confluence server, lacking essential operations like create, update, or delete pages. While the tools cover basic read/search functionality, the scope is incomplete for typical content management workflows.
The tool surface is significantly incomplete for a Confluence domain. It only supports listing, reading, and searching content, with no ability to create, update, or delete pages, spaces, or attachments. This will cause agent failures in common content management tasks.