Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_confluenceB | Search for content across allowed Confluence spaces by text and/or title |
| get_pageC | Retrieve a specific Confluence page by ID |
| create_pageC | Create a new Confluence page |
| update_pageC | Update an existing Confluence page |
| move_pageC | Move a Confluence page to a different space or parent |
| list_spacesC | List all accessible Confluence spaces (filtered by allowed spaces) |
| get_space_by_idC | Get detailed information about a specific Confluence space by ID |
| get_space_by_keyB | Get detailed information about a specific Confluence space by key |
| get_space_contentC | Get pages from a specific space |
| get_page_childrenC | Get child pages of a specific page |
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
Most tools have distinct purposes, but there is some potential confusion between get_space_by_id and get_space_by_key which serve similar functions with different identifiers, and get_space_content overlaps conceptually with listing pages in a space. However, descriptions clarify the distinctions, preventing major misselection.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions (e.g., create_page, get_page, list_spaces). There are no deviations in style or convention, making the set predictable and easy to understand.
With 10 tools, the server is well-scoped for managing Confluence content, covering core operations like CRUD for pages, space management, and search. Each tool has a clear role without bloat or redundancy.
The tool set provides strong coverage for page and space operations, including create, read, update, move, and search. Minor gaps exist, such as no delete_page tool or advanced space management (e.g., create_space), but agents can handle most workflows effectively.