@ama-work/mcp-atlassian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATEWAY_PSK | No | Your pre-shared key for the registry. | |
| INSTANCE_ID | No | Your instance ID for the registry. | |
| REGISTRY_URL | No | URL of the ama-mcp-registry. | |
| ATLASSIAN_CLOUD_ID | No | Your Atlassian cloud ID. | |
| ATLASSIAN_ACCESS_TOKEN | No | Your Atlassian OAuth access 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 |
|---|---|
| jira_search_issuesA | Search Jira issues using JQL. Returns a list of matching issues with key, summary, status, assignee, and priority. |
| jira_get_issueA | Get full details of a single Jira issue by its key (e.g. PROJ-123). Returns fields including summary, description, status, assignee, comments, and subtasks. |
| jira_create_issueA | Create a new Jira issue in the specified project. |
| jira_update_issueC | Update fields on an existing Jira issue. |
| jira_transition_issueA | Move a Jira issue to a new status by triggering a workflow transition (e.g. In Progress, Done). |
| jira_add_commentB | Add a comment to a Jira issue. |
| jira_get_projectsA | List all Jira projects accessible to the authenticated user. Returns project key, name, type, and lead. |
| confluence_searchA | Search Confluence content using CQL (Confluence Query Language). Returns matching pages, blog posts, and spaces with title, spaceKey, URL, and a short excerpt. |
| confluence_get_pageA | Get the full content of a Confluence page by its numeric page ID. Returns title, spaceKey, body as markdown, version number, and last-modified date. |
| confluence_create_pageA | Create a new Confluence page in the specified space. |
| confluence_update_pageA | Update the title and/or content of an existing Confluence page. Requires the current version number — Confluence rejects updates that omit it. |
| confluence_add_commentB | Add a footer comment to a Confluence page. |
| confluence_get_spacesA | List Confluence spaces accessible to the authenticated user. Returns space ID, key, name, type, and homepage ID. |
| atlassian_whoamiA | Returns the identity of the currently authenticated Atlassian user — account ID, display name, email, and accessible site URLs. |
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 14 tools
Every tool is clearly scoped by domain prefix (jira_, confluence_, atlassian_) and a distinct action, so there is no real overlap. Similar tools like jira_add_comment and confluence_add_comment are separated by their domain prefix, and analogous tools like jira_get_projects vs confluence_get_spaces target different resources.
Tool names follow a predictable domain_verb_noun pattern in snake_case, such as jira_search_issues and confluence_create_page. The only minor deviation is atlassian_whoami, which uses a command-style noun rather than a verb_noun structure, but it remains readable and clearly namespaced.
14 tools is well within the ideal range and appropriately covers two product areas (Jira and Confluence) plus an identity check. Each tool serves a distinct purpose and none feel redundant or excessive for the server's broad Atlassian scope.
The tool surface covers core Jira and Confluence workflows: search, create, read, update, transition/comment, plus project/space discovery and identity. Minor gaps exist such as no delete operations, no listing of available Jira transitions, and no page comment retrieval, but agents can still accomplish most common tasks without dead ends.