confluence-dc-advops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_HOST | Yes | The host URL for Confluence Data Center (e.g., https://localhost:8443) | |
| CONFLUENCE_API_TOKEN | No | API token for authentication. If not provided, the server will attempt to retrieve from macOS Keychain. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| confluence_movePageA | Move (reparent) a Confluence Data Center page under a new parent. Uses PUT /rest/api/content/{id} with ancestors. Does not change page body. |
| confluence_movePagesA | Move several Confluence pages under new parents, sequentially. Each item reports success/error. |
| confluence_getStorageToFileB | Download Confluence page body.storage XML to a local file for surgical edits (large templates). Returns version/title/path. Prefer this over stuffing huge storage into chat. |
| confluence_updateStorageFromFileA | Publish page body from a local storage XML file via the Confluence proxy (same auth as confluence-dc). Auto-increments version unless you pass version (= current+1). Pass content as-is — do not re-escape entities. Optional parentId to reparent in the same PUT. |
| confluence_listSpaceTemplatesA | List space page templates via /rest/experimental/template/page (DC). Use spaceKey=TempStream for ДРП Create from template. Optional nameContains filter. Does not expand body by default (fast). |
| confluence_getSpaceTemplateToFileA | Download a space page template body.storage to a local XML file. Requires spaceKey (GET by id alone 404s on DC). Identify by templateId and/or exact/partial name. |
| confluence_createSpaceTemplateFromFileA | Create a new space page template from a local storage XML file via POST /rest/experimental/template. Use after a new BSA заготовка exists and needs a TempStream Create-from-template entry. Fails if a template with the same name already exists. |
| confluence_updateSpaceTemplateFromFileA | Update a space page template body from a local storage XML file via PUT /rest/experimental/template. Preserves labels by default. BSA page remains source of truth — this publishes a snapshot for Create from template. To rename: pass templateId + new |
| confluence_syncPageToSpaceTemplateB | Fast path: copy body.storage from a BSA/page contentId into a TempStream space template (Create from template snapshot). Example: contentId=259706536 (Заготовка BRD) → templateId=227016711 (CR-XXX-BRD) spaceKey=TempStream. |
| confluence_deleteSpaceTemplateA | DESTRUCTIVE. Delete one TempStream/space Create template (DELETE /rest/experimental/template/{id}). ALWAYS stop and get explicit human approval in chat first — never invent confirm. Requires confirm="DELETE" and confirmName=exact template name. No trash restore; archive dump first. |
| confluence_deleteSpaceTemplatesA | DESTRUCTIVE. Delete several space Create templates by id. ALWAYS get explicit human approval in chat first. Requires confirm="DELETE" and confirmNames[] exact names (same order as templateIds). Continues on per-item errors. Archive dump first. |
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 11 tools
Every tool targets a distinct action and resource: storage file operations, page moving (single/multiple), and space template lifecycle (list, get, create, update, sync, delete). The destructive delete tools further differentiate with explicit approval requirements. No two tools cause confusion.
All tool names follow a consistent 'confluence_verbNoun' pattern with camelCase after the underscore (e.g., confluence_updateStorageFromFile, confluence_movePages). The pattern is uniform and predictable, aiding agent selection.
With 11 tools, the set is well-scoped for the domain of Confluence Data Center advanced operations, particularly around storage XML and space templates. Each tool serves a clear purpose without unnecessary overlap, making the count appropriate.
The tool surface covers the core workflows for managing storage XML files and space templates (CRUD, sync, move, delete). Minor gap: no tool to create a page from a template, but that aligns with the server's focus on template management rather than page creation. Overall, it's nearly complete for its stated purpose.