a2atlassian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_TOKEN | No | Your Atlassian API token for authentication with Jira and Confluence |
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 |
|---|---|
| loginA | Save an Atlassian connection. Validates by calling /myself. For security, prefer passing token as ${ENV_VAR} reference (e.g., "${ATLASSIAN_TOKEN}") rather than a literal value. The variable is expanded at runtime, never stored resolved. |
| logoutC | Remove a saved connection. |
| list_connectionsC | List saved connections (no secrets shown). |
| jira_get_issueC | Get a Jira issue by key. Returns full issue data including fields and status. |
| jira_searchC | Search Jira issues using JQL. Returns list of matching issues. |
| jira_get_commentsC | Get all comments for a Jira issue. |
| jira_get_transitionsC | Get available transitions for a Jira issue. |
| jira_add_commentB | Add a comment to a Jira issue. Uses wiki markup (API v2). |
| jira_edit_commentC | Edit an existing comment on a Jira issue. Uses wiki markup (API v2). |
| jira_transition_issueA | Transition a Jira issue to a new status. Use jira_get_transitions to discover available transitions. |
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 10 tools
Each tool has a distinct purpose with clear boundaries. Comment operations (add/edit/get) are well differentiated, issue retrieval is separate from workflow transitions, and connection management stands apart from Jira operations.
All tools use consistent snake_case formatting. Jira operations follow a clear jira_verb_noun pattern, while connection management tools use simpler verbs (login/logout/list_connections). The distinction between prefixed and unprefixed tools is logical but creates a minor inconsistency in the naming scheme.
Ten tools represents an appropriate scope for a Jira integration—sufficient to cover comment management, issue retrieval, workflow transitions, and authentication without bloat or fragmentation.
The surface covers reading, commenting, and workflow transitions well, but lacks essential write operations for issues themselves—specifically create_issue and update_issue (for fields). This creates a significant functional gap where agents can comment on and move issues but cannot create or modify issue content.