awesome-confluence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFLUENCE_URL | Yes | The URL of your Confluence instance (e.g., https://your-domain.atlassian.net) | |
| CONFLUENCE_EMAIL | Yes | Your Atlassian account email address used for authentication | |
| CONFLUENCE_API_TOKEN | Yes | The API token generated from your Atlassian 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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_spacesB | List all Confluence spaces accessible to the authenticated user. |
| search_pagesB | Search for Confluence pages by title or content. |
| fetch_page_markdownA | Fetch a Confluence page and convert it to Markdown format. This tool retrieves page content and converts it from HTML to Markdown, reducing token usage by 60-80% compared to raw HTML while preserving formatting, links, and structure. |
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 3 tools
Each tool serves a distinct purpose: fetching a specific page, listing spaces, and searching pages. No overlap exists.
All tools use consistent snake_case naming with clear verb-noun patterns: fetch_page_markdown, list_spaces, search_pages.
Only 3 tools for a Confluence API server is thin. Common operations like creating, updating, or deleting pages are missing.
The server covers only read operations (fetch, list, search). No create, update, or delete tools, leaving significant gaps for agent workflows.