Jira & Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | The URL of your Atlassian Jira instance | |
| JIRA_CLOUD | No | Set to 'true' for cloud version, 'false' for server version | |
| JIRA_USERNAME | No | Your Jira email address | |
| CONFLUENCE_URL | No | The URL of your Atlassian Confluence instance | |
| JIRA_API_TOKEN | No | Your Jira API token (generate at https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) | |
| CONFLUENCE_CLOUD | No | Set to 'true' for cloud version, 'false' for server version | |
| CONFLUENCE_USERNAME | No | Your Confluence email address | |
| CONFLUENCE_API_TOKEN | No | Your Confluence API token (generate at https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_search_issuesC | Search for Jira issues using JQL |
| jira_get_issueC | Get details of a specific Jira issue |
| jira_create_issueC | Create a new Jira issue |
| jira_update_issueC | Update an existing Jira issue |
| jira_add_commentC | Add a comment to a Jira issue |
| jira_transition_issueC | Transition a Jira issue to a different status |
| jira_get_projectsA | Get list of Jira projects |
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 7 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific Jira action (e.g., create, get, update, search, transition, add comment, list projects) with no overlap in functionality. The descriptions make it easy to differentiate between tools like jira_update_issue and jira_transition_issue.
All tools follow a consistent verb_noun pattern with a 'jira_' prefix (e.g., jira_create_issue, jira_get_issue). The naming is predictable and readable throughout, using snake_case uniformly without any deviations or mixed conventions.
The 7 tools are well-scoped for a Jira-focused server, covering core operations without being excessive. Each tool earns its place by addressing essential Jira workflows (e.g., issue lifecycle, project management, searching). This count is appropriate for the domain, avoiding both thinness and bloat.
The tool set provides strong coverage for Jira operations, including CRUD for issues (create, get, update), search, transitions, comments, and project listing. A minor gap is the lack of tools for Confluence (implied by the server name), but for Jira alone, it's nearly complete with only small omissions like deleting issues or managing users.