confluence-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_URL | Yes | Base URL of your Confluence instance | |
| CONFLUENCE_MCP_HOST | No | Bind address (HTTP mode) | 0.0.0.0 |
| CONFLUENCE_MCP_PORT | No | Listen port (HTTP mode) | 43043 |
| CONFLUENCE_CACHE_DIR | No | Cache directory path | .cache/confluence_mcp |
| CONFLUENCE_VERIFY_TLS | No | Enforce TLS certificate validation | true |
| CONFLUENCE_MAX_RETRIES | No | Retry attempts for transient failures | 3 |
| CONFLUENCE_CACHE_ENABLED | No | Enable/disable disk cache | true |
| CONFLUENCE_MCP_TRANSPORT | No | Transport type: stdio, http, sse, or streamable-http | stdio |
| CONFLUENCE_REQUEST_TIMEOUT | No | HTTP timeout in seconds | 20 |
| CONFLUENCE_CACHE_TTL_SEARCH | No | Search cache TTL (seconds) | 300 |
| CONFLUENCE_CACHE_TTL_CONTENT | No | Page content cache TTL (seconds) | 900 |
| CONFLUENCE_PERSONAL_ACCESS_TOKEN | Yes | Bearer token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_confluenceB | Execute a highlighted CQL search via the shared Confluence orchestrator. |
| fetch_confluence_pageA | Hydrate a Confluence page’s storage body, version data, and ancestry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Fetch and search are completely distinct operations: one retrieves a specific page by ID, the other finds pages via CQL. There is no ambiguity between the two.
Both names follow a verb_prefix pattern in snake_case, but 'fetch_confluence_page' includes an extra object while 'search_confluence' does not. This is a minor inconsistency, but still predictable.
Only two tools for a Confluence server feels too thin. A typical integration requires at least page creation, updates, and space management, not just fetch and search.
The server covers only read-oriented operations (fetch a page, search) and lacks all write capabilities such as create, update, delete, or list spaces. This is a significant gap for a domain like Confluence.