Confluence Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_HOST | Yes | Your Confluence host URL, e.g. https://your-team.atlassian.net | |
| CONFLUENCE_EMAIL | Yes | Your Confluence email | |
| CONFLUENCE_API_TOKEN | Yes | Your Confluence API token |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| manage_confluence_pageC | Get, create, update, delete, move, copy, archive, or pull pages for editing. Read and add comments. Manage labels and content properties. Create returns a scratchpad for composing content before publishing. Use pull_for_editing to load existing page content into a scratchpad. Archive/unarchive pages or entire page trees. |
| edit_confluence_contentB | Line-addressed content editing within a scratchpad buffer. View, insert, replace, or remove lines, then submit to Confluence. Requires a scratchpadId from create or pull_for_editing. |
| manage_confluence_spaceC | List spaces, get space details, or manage space configuration. |
| search_confluenceA | Search Confluence using CQL (Confluence Query Language), full-text search, or filter by labels/contributors. |
| manage_confluence_mediaB | Upload, download, list, view, or delete page attachments and media. Use view to display images inline. |
| navigate_confluenceA | Navigate page hierarchy, discover links, backlinks, and related pages. Returns tree views and relationship graphs. |
| queue_confluence_operationsA | Batch multiple Confluence operations in a single call. Supports result references ($0.pageId) and per-operation error strategies. |
| manage_workspaceA | Stage files in the local workspace for attachment operations. List, read, write, delete files, or create directories. Supports nested paths (e.g. "projects/images/photo.png"). Downloaded attachments land here; upload can read from here. All responses include the absolute filesystem path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Macros | Confluence macro registry with parameter schemas and usage examples |
| Instance Summary | Confluence instance overview: available spaces, GraphQL status |
| Tool Documentation | Complete documentation for all Confluence MCP tools with operations and examples |
TDQS
Scored across 8 tools
Most tools are clearly distinct, but manage_confluence_page and edit_confluence_content both involve editing page content. The descriptions clarify that edit_confluence_content operates on scratchpad buffers only, so agents can differentiate, though the boundary could confuse.
All tools follow a consistent verb_noun snake_case pattern (e.g., manage_confluence_page, search_confluence). Even the slightly different navigate_confluence and queue_confluence_operations fit the verb-based style without breaking the pattern.
8 tools is well within the ideal range for a domain server. Each tool covers a meaningful area—pages, media, workspace, navigation, batching, search, content editing, and spaces—without unnecessary fragmentation.
The surface covers core Confluence workflows: page lifecycle, media, spaces, search, navigation, and batching. Minor gaps exist such as explicit permission/user management, but the included operations handle most common needs and comments are coverable through the page tool.