confluence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_URL | Yes | Your Confluence instance URL | |
| CONFLUENCE_CLOUD | No | true for Cloud, false for Server | true |
| CONFLUENCE_TOKEN | Yes | Your API token or password | |
| CONFLUENCE_USERNAME | Yes | Your username or email |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search Confluence content |
| get_pageC | Get Confluence page content |
| get_page_childrenB | Get child pages of a Confluence page |
| get_attachmentsB | Get attachments from a Confluence page |
| download_attachmentB | Download a Confluence attachment |
| get_commentsB | Get comments from a Confluence page |
| add_commentB | Add a comment to a Confluence page |
| create_pageC | Create a new Confluence page |
| update_pageA | Update a Confluence page with new content. IMPORTANT: For large HTML files, use 'content_file' parameter to provide the file path. The tool automatically handles:
|
| upload_attachmentA | Upload a file as an attachment to a Confluence page. The file must be specified by its absolute path on the local filesystem. Optionally embed the attachment in the page body. |
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 10 tools
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.
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.
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.
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.