confluence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_URL | Yes | REST API base URL, e.g. https://wiki.example.com/rest/api | |
| CONFLUENCE_TOKEN | Yes | Personal Access Token | |
| CONFLUENCE_VERIFY_SSL | No | true (default) / false | true |
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 |
|---|---|
| get_content_by_idA | Get content by ID. Returns title, body (storage format HTML), space, version, ancestors, child pages, attachments. |
| download_attachmentC | Download attachment content. |
| get_spacesB | Get spaces. Returns key and name. Filter by space_key, status, label, favourite. |
| get_commentsA | Get comments on a page or comment thread by content ID. Returns footer and inline comments. Inline comments have markerRef — UUID of ac:inline-comment-marker in page body.storage. Pass a comment ID to get its reply thread. |
| searchA | Search Confluence. All filters are combined with AND. For paginated results use start/limit params; check hasMore in the response. |
| get_userA | Get user profile by username or userKey. Returns displayName, username, userKey. |
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 6 tools
Each tool targets a distinct resource and action: content, attachment, spaces, comments, search, and user. There is no overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun snake_case pattern, with verbs like get, download, and search. The naming convention is uniform and predictable.
Six tools is a well-scoped number for a Confluence integration, covering core read operations without being excessive. Each tool earns its place.
The surface covers read-only operations for content, comments, spaces, users, attachments, and search. However, there are no create, update, or delete operations, which is a notable gap for a full Confluence API.