confluence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_BASE_URL | Yes | The base URL of your Confluence instance, e.g., https://your-domain.atlassian.net | |
| CONFLUENCE_SYNC_DIR | No | Default directory for syncing docs | ./confluence-docs |
| CONFLUENCE_API_TOKEN | Yes | Your API token for authentication | |
| CONFLUENCE_SPACE_KEY | No | Default space key for operations (optional if space key is provided in tool arguments) | |
| CONFLUENCE_PAGE_LIMIT | No | Default page limit for queries | 10 |
| CONFLUENCE_USER_EMAIL | Yes | Your email address associated with the Confluence account |
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 |
|---|---|
| search_confluenceC | Search Confluence for pages matching a query using CQL (Confluence Query Language) |
| get_page_by_idA | Get a Confluence page by its ID with full content |
| get_page_by_titleA | Get a Confluence page by title within a space |
| get_space_pagesA | Get all pages in a Confluence space |
| get_page_childrenA | Get child pages of a parent page |
| sync_confluence_docsA | Sync Confluence pages to local markdown files. Can sync a space, search results, or specific pages. |
| push_md_to_confluenceA | Push markdown files to Confluence. Creates new pages or updates existing ones based on frontmatter or title/space. |
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 7 tools
Each tool targets a distinct operation: retrieval by ID, by title, listing space pages, listing children, search, importing from Confluence, and exporting to Confluence. There is no meaningful overlap, and the descriptions make the boundaries clear.
All tool names use snake_case and follow a clear pattern: get_* for retrieval operations, search_* for querying, sync_* and push_* for transfer operations. The naming is consistent and predictable.
With 7 tools, the server is well-scoped. Each tool serves a necessary function for reading, searching, and syncing Confluence content, without unnecessary bloat or redundancy.
The tool set covers the primary lifecycle for Confluence content: read (by id, title, space, children, search) and write/update via push_md_to_confluence. The main gap is lack of a direct delete or page management operation, but the core workflows are well supported.