A
licenseA
qualityC
maintenanceMCP 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.
15
37 npm
ISC
confluence-http-api-mcp
by rkorablin
Related Servers
Alternatives to confluence-http-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to read Confluence page content by URL, supporting self-hosted Confluence with basic auth.-
- 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
- FlicenseAqualityBmaintenanceA read-only MCP server for Jira and Confluence Cloud, providing atlassian_get and jira_search tools.21,031 npm-
- AlicenseNot gradedqualityBmaintenanceMCP server for reading Confluence Server/DC documents with search, page content, metadata, spaces, page tree, and attachment/image support.8 npmMIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables querying and searching Atlassian Confluence pages and Jira issues through their REST APIs. Supports retrieving content by ID or URL, searching using CQL/JQL, and listing spaces and projects.1MIT
TDQS
A4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a distinct resource or access pattern: search uses CQL, get_page uses numeric ID, get_page_by_title uses space+title, list_spaces enumerates spaces, and get_page_children navigates hierarchy. No two tools overlap in purpose.
Naming Consistency5/5
All tools use a consistent 'confluence_' prefix followed by a verb_noun pattern. The two get_page variants are differentiated by suffix 'by_title', maintaining clarity.
Tool Count5/5
Five tools is well-scoped for a read-only Confluence integration; each tool serves a distinct function without redundancy or excessive minimalism.
Completeness4/5
The core read operations are present: search, get by ID, get by title, list spaces, and list children. However, there are no mutation endpoints and no space-level detail tool, leaving minor gaps for a full API surface.
Maintenance
ActivityInactive
ResponsivenessNo issues