atlassian-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_EMAIL | Yes | The email address associated with your Atlassian account | |
| ATLASSIAN_SITE_URL | Yes | The base URL of your Atlassian site, e.g., https://your-company.atlassian.net | |
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian Cloud 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| atlassian_getA | Make one authenticated GET request to a site-relative Jira or Confluence API path. This tool is read-only and may truncate large output. |
| jira_searchA | Search Jira issues using POST /rest/api/3/search/jql. This is the only read-only POST exposed by the server. Returns Jira's raw response and may truncate large output. |
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 serve distinct purposes: one is a generic authenticated GET for any Jira or Confluence path, while the other is specifically a Jira JQL search. Although there is some overlap in that the GET could be used for search, the specific search tool is clearly targeted at JQL queries, making confusion unlikely.
The naming is inconsistent: one tool uses the 'atlassian_' prefix while the other uses 'jira_', and the verbs 'get' and 'search' do not follow a clear pattern. With only two tools, the lack of a unified convention is noticeable and could confuse agents expecting a consistent prefix.
Two tools is borderline thin for a server covering Atlassian's broad API surface, but it is not extreme enough to warrant a 1 or 2. The count is on the low end, feeling somewhat sparse but not entirely unreasonable for a focused read-only utility.
The server only offers read-only operations: a generic GET and a Jira search. It lacks write capabilities, Confluence-specific search, and any other common Atlassian operations, making it significantly incomplete for a platform with such a wide API. Agents would frequently hit dead ends when needing update or create functionality.