Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_URL | Yes | Your Confluence instance URL (e.g., https://yourname.atlassian.net) | |
| CONFLUENCE_EMAIL | Yes | Your Atlassian account email | |
| CONFLUENCE_API_TOKEN | Yes | Your Confluence API token (https://id.atlassian.com/manage-profile/security/api-tokens) | |
| CONFLUENCE_SPACE_KEY | No | Default space key (optional, can be passed per-tool) |
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 |
|---|---|
| create_confluence_pageC | Create a new page in Confluence. Supports Markdown content which will be converted to Confluence format. |
| update_confluence_pageC | Update an existing page in Confluence |
| get_confluence_pageC | Get the content of a Confluence page by ID |
| delete_confluence_pageA | Delete a Confluence page by ID. Use with caution! |
| search_confluence_pagesC | Search for pages in a Confluence space by title |
| list_confluence_pagesC | List all pages in a Confluence 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 6 tools
Every tool has a clearly distinct purpose with no ambiguity: create, delete, get, list, search, and update are all unique actions targeting Confluence pages. The descriptions reinforce this with specific functions like 'create a new page', 'delete by ID', 'get content by ID', 'list all pages', 'search by title', and 'update an existing page'.
Tool names follow a perfectly consistent verb_noun pattern throughout, all using snake_case with the format 'action_confluence_page' (e.g., create_confluence_page, delete_confluence_page). This predictability makes it easy for agents to understand and select tools without confusion.
With 6 tools, this server is well-scoped for managing Confluence pages, covering essential CRUD operations (create, get, update, delete) plus listing and searching. Each tool earns its place without being excessive or insufficient for the domain, fitting typical expectations of 3-15 tools.
The tool surface provides complete CRUD/lifecycle coverage for Confluence pages, including create, read (get, list, search), update, and delete. There are no obvious gaps or dead ends, as agents can perform all core operations needed to manage pages in this domain effectively.