Atlassian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_searchA | Search for Jira work items using JQL (Jira Query Language). Use to find issues by project, status, assignee, priority, created/updated dates, and more. Returns a list of matching work items with their key, summary, status, priority, and assignee. Common search patterns: 1) My work: 'assignee = currentUser()' 2) My active work: 'assignee = currentUser() AND status NOT IN (Done, Closed)' 3) Project issues: 'project = SSAS' 4) High priority: 'priority = High' or 'priority IN (High, Highest)' 5) Recent updates: 'updated >= -7d' (last 7 days) 6) Combine with AND/OR: 'project = SSAS AND status = Open AND assignee = currentUser()' 7) Sort results: add 'ORDER BY updated DESC' or 'ORDER BY priority DESC, created ASC' |
| jira_get_issueA | Retrieve detailed information about a specific Jira work item. Shows all fields including description, reporter, watchers, attachments, linked issues, and full history. |
| jira_commentA | Add a comment to a Jira work item. Use to provide status updates, ask questions, or share information with the team working on the issue. |
| jira_update_statusB | Transition a Jira work item to a new status (e.g., 'In Progress', 'Done', 'Blocked'). Use to move work items through your workflow. |
| jira_assignB | Assign a Jira work item to a user. Use to delegate tasks and clarify ownership of work items. |
| jira_set_fieldB | Update a custom field value on a Jira work item. Use to set fields like components, fix versions, labels, environment, etc. |
| jira_add_labelA | Add a label/tag to a Jira work item. Use to categorize and organize work items for easier filtering and tracking. |
| jira_remove_labelB | Remove a label/tag from a Jira work item. Use to clean up or reorganize issue categorization. |
| jira_link_issueA | Create a link between two Jira work items to show relationships. Use to track dependencies, blocking relationships, or related work. |
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 9 tools
Every tool has a clearly distinct purpose targeting specific Jira operations with no overlap. For example, jira_add_label and jira_remove_label are complementary but distinct, while jira_get_issue, jira_search, and jira_update_status each handle different aspects of issue management. The descriptions reinforce these boundaries, making misselection unlikely.
All tools follow a consistent 'jira_verb_noun' pattern using snake_case throughout. The verbs are specific and descriptive (e.g., add, assign, comment, get, link, remove, search, set, update), creating a predictable and readable naming convention across the entire set.
With 9 tools, the server is well-scoped for Jira operations, covering core workflows without bloat. Each tool earns its place by addressing a specific need in issue management, from retrieval and search to updates and relationships, making the count appropriate for the domain.
The toolset provides strong coverage for common Jira workflows, including CRUD-like operations (get, search, update status, set fields), collaboration (comment, assign), and organization (labels, links). A minor gap exists in missing explicit create or delete issue tools, but agents can work around this using jira_set_field or other methods for creation, and the surface otherwise supports most agent tasks effectively.