confluence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Your JIRA URL (e.g., https://XXXXXXXX.atlassian.net) | |
| CONFLUENCE_URL | Yes | Your Confluence URL (e.g., https://XXXXXXXX.atlassian.net) | |
| CONFLUENCE_API_KEY | Yes | Your Confluence API key can be acquired from https://id.atlassian.com/manage-profile/security/api-tokens | |
| CONFLUENCE_API_MAIL | Yes | Your email address for the Confluence API. |
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 |
|---|---|
| execute_cql_searchC | Execute a CQL query on Confluence to search pages |
| get_page_contentB | Get the content of a Confluence page |
| create_pageB | Create a new Confluence page |
| update_pageB | Update an existing Confluence page |
| execute_jql_searchB | Execute a JQL query on Jira to search issues |
| create_jira_issueC | Create a new Jira issue |
| update_jira_issueB | Update an existing Jira issue |
| transition_jira_issueB | Change the status of a Jira issue |
| get_board_sprintsB | Get all sprints from a Jira board |
| get_sprint_issuesC | Get all issues from a sprint |
| get_current_sprintA | Get current active sprint from a board with its issues |
| get_epic_issuesB | Get all issues belonging to an epic |
| get_user_issuesB | Get all issues assigned to or reported by a specific user in a board |
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 13 tools
Each tool targets a distinct operation and domain, with clear separation between Confluence page management and Jira issue tracking. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like create, get, update, execute, and transition appropriately paired with nouns like page, jira_issue, cql_search, etc.
With 13 tools covering both Confluence and Jira operations, the count is well-scoped and balanced—each tool serves a distinct purpose without being overwhelming or insufficient.
The tool set covers essential CRUD operations for both Confluence pages and Jira issues, along with context-specific searches. Missing delete operations and some Jira board management are minor gaps, but core workflows are supported.