F
licenseA
qualityF
maintenanceEnables interaction with Jira and Confluence APIs to search, create, and manage issues, pages, comments, and attachments across both Atlassian platforms.
7
-
confluence-mcp
by lucaszzz1202
Related Servers
Alternatives to confluence-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides read access to Confluence Server/Data Center pages, sections, tables, and search via the Confluence REST API v1.-
- AlicenseAqualityAmaintenanceEnables interaction with Atlassian Jira and Confluence via their REST API, providing tools for searching, creating, updating, commenting, and retrieving issues, pages, projects, and spaces.1412 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Atlassian Confluence through MCP, allowing retrieval of pages by ID and searching with CQL queries.88 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables interacting with a self-hosted Confluence Data Center instance to search pages using CQL, retrieve pages and children, and create or update page content via the Confluence REST API.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read Confluence Cloud pages as markdown, browse page trees, download image attachments, and diff content against local documentation.MIT
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct resource and action: search, page retrieval, children, attachments (list vs download), comments (list vs add), page create/update, and attachment upload. No two tools appear to do the same thing.
Naming Consistency4/5
Most names follow a clear verb_noun pattern (get_page, create_page, update_page, upload_attachment). The mix of verbs like search, get, download, add, create, update, upload is reasonable and readable, though not perfectly uniform.
Tool Count5/5
With 10 tools, the set is well-scoped for a Confluence MCP server covering search, page content, comments, and attachments. Each tool has a clear role without feeling excessive.
Completeness3/5
Core content operations are covered (search, read, create, update, comment, attachments), but there are no delete operations for pages, comments, or attachments. This is a notable gap for full lifecycle management, though typical workflows are still possible.
Maintenance
ActivityInactive
ResponsivenessNo issues