confluence-wiki-mcp-server
Related Servers
Alternatives to confluence-wiki-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for searching and retrieving pages from Atlassian Confluence.41 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for administering Atlassian Confluence Cloud wiki pages, supporting CRUD operations, page navigation, comments, attachments, and more.621GPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server for reading Confluence Server/DC documents with search, page content, metadata, spaces, page tree, and attachment/image support.3 npmMIT
- 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
- AlicenseAqualityDmaintenanceMCP server for Confluence Cloud/Server/Data Center, enabling page search, CQL queries, page CRUD, attachment upload, and user identity lookup.23392 npm4MIT
- FlicenseAqualityCmaintenanceMCP server for Confluence REST API enabling page retrieval, attachment downloads, space listing, comment access, and full-text search via tools.6-
TDQS
Scored across 13 tools
Most tools have distinct purposes (search, fetch, get comments, etc.), but there is minor overlap between `get_wiki_attachments` and `get_wiki_assets`, both listing files, which could cause confusion.
Tools follow a verb_noun pattern (e.g., `fetch_wiki_page`, `search_wiki`), but `wiki_auth_login`, `wiki_auth_logout`, and `wiki_health_check` deviate from the standard prefix, mixing `wiki_` with verbs inconsistently.
With 13 tools, the scope is well-balanced for a Wiki MCP server, covering necessary functions like search, retrieval, authentication, and asset management without being bloated.
The server excels at read and evidence-gathering operations but lacks write capabilities (e.g., create, update, delete pages or attachments), limiting its completeness for full Wiki lifecycle management.