MCP Atlassian Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Your Jira URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_USERNAME | Yes | Your Jira username/email (e.g., your-email@domain.com) | |
| CONFLUENCE_URL | Yes | Your Confluence URL (e.g., https://your-domain.atlassian.net/wiki) | |
| JIRA_API_TOKEN | Yes | Your Jira API token | |
| CONFLUENCE_USERNAME | Yes | Your Confluence username/email (e.g., your-email@domain.com) | |
| 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| confluence_searchC | Search Confluence content using CQL |
| jira_searchC | Search Jira issues using JQL |
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 2 tools
The two tools are clearly distinct: one searches Confluence content using CQL, and the other searches Jira issues using JQL. There is no overlap in purpose or target resource, making misselection highly unlikely.
Both tools follow a consistent naming pattern: [product]_[action] (confluence_search, jira_search). This verb_noun style is uniform and predictable across the set.
With only two tools, the server feels thin for covering Atlassian's ecosystem. While Confluence and Jira are major products, the lack of additional operations (e.g., create, update, delete) or coverage of other Atlassian tools (e.g., Bitbucket, Trello) makes the scope appear incomplete.
The server only provides search functionality for two Atlassian products, missing essential CRUD operations (e.g., create pages in Confluence, update issues in Jira) and other lifecycle actions. This creates significant gaps that will limit agent workflows and likely cause failures in broader tasks.