MCP Jira & Confluence Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | Base URL of your Jira instance (e.g., https://yourcompany.atlassian.net) | |
| JIRA_USERNAME | No | Your Jira username/email | |
| CONFLUENCE_URL | No | Base URL of your Confluence instance (e.g., https://yourcompany.atlassian.net/wiki) | |
| JIRA_API_TOKEN | No | Your Jira API token or password | |
| CONFLUENCE_USERNAME | No | Your Confluence username/email | |
| JIRA_PERSONAL_TOKEN | No | Personal access token (alternative to username/API token) | |
| CONFLUENCE_API_TOKEN | No | Your Confluence API token or password | |
| CONFLUENCE_PERSONAL_TOKEN | No | Personal access token (alternative to username/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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-jira-issueC | Create a new Jira issue |
| comment-jira-issueC | Add a comment to a Jira issue |
| transition-jira-issueC | Transition a Jira issue to a new status |
| get-jira-issueB | Get detailed information about a specific Jira issue by its key |
| get-my-assigned-issuesA | Get issues assigned to the current user, ordered by priority (highest first) and creation date (newest first) |
| summarize-jira-issueB | Get a comprehensive summary of a Jira issue including comments, status history, and any Confluence page references |
| extract-confluence-linksA | Extract all Confluence page links and Git repository URLs referenced in a Jira issue (from description, comments, and remote links) |
| create-confluence-pageC | Create a new Confluence page |
| update-confluence-pageB | Update an existing Confluence page. If version is not provided, the current version will be automatically fetched to prevent conflicts. |
| comment-confluence-pageC | Add a comment to a Confluence page |
| get-confluence-pageA | Get a Confluence page by ID or title. Use this tool to retrieve a specific page's content, optionally including comments and version history. |
| search-confluenceA | Search Confluence pages using CQL (Confluence Query Language). Simple queries are automatically enhanced with proper CQL syntax (e.g., 'API docs' becomes 'text ~ "API docs" OR title ~ "API docs"'). Advanced CQL is used as-is. |
| ask-confluence-pageB | Ask a question about a specific Confluence page content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-jira-issue | Creates a summary of a Jira issue |
| create-jira-description | Creates a well-structured description for a Jira issue |
| summarize-confluence-page | Creates a summary of a Confluence page |
| create-confluence-content | Creates well-structured content for a Confluence page |
| answer-confluence-question | Answer a question about a specific Confluence page using its content |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets either Jira or Confluence with distinct actions, making them easily distinguishable. Even similar tools like get-jira-issue and summarize-jira-issue have clear differences in scope.
All tools follow a consistent verb-noun pattern with hyphens, e.g., 'create-confluence-page' and 'transition-jira-issue', ensuring predictability.
13 tools provide a balanced coverage for Jira and Confluence operations without being excessive. Each tool serves a clear purpose.
Covers core CRUD for Confluence pages and Jira issues, plus commenting, searching, transitions, and extra utilities. Missing delete operations and Jira issue field updates are minor gaps.