Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your email (Cloud) or username (Server) | |
| JIRA_BASE_URL | Yes | Your Jira site URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_API_TOKEN | Yes | API token (Cloud) or Personal Access Token (Server) | |
| JIRA_AUTH_TYPE | Yes | Authentication type: 'cloud' or 'server' |
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 |
|---|---|
| search_issuesA | Search Jira issues using JQL. Returns key, summary, status, assignee, priority, and type. |
| get_issueA | Get full details of a single Jira issue by its key (e.g. PROJ-123). |
| create_issueB | Create a new Jira issue in a project. |
| update_issueB | Update fields on an existing Jira issue. |
| add_commentC | Add a comment to a Jira issue. |
| get_transitionsA | Get available status transitions for an issue (useful before transitioning). |
| transition_issueA | Transition a Jira issue to a new status. Use get_transitions first to find the right transition ID. |
| assign_issueA | Assign a Jira issue to a user. For Cloud use accountId, for Server use username. |
| list_projectsA | List all Jira projects accessible to the authenticated user. |
| get_myselfA | Get the profile of the currently authenticated Jira user. |
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 clear, distinct purpose: search vs. get, create vs. update, comment, transitions, assignment, project listing, and user profile. There is no ambiguity between tools; an agent can reliably select the correct one based on the action needed.
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_issues, get_issue, create_issue, add_comment). Even the 'get_*' tools differ by object (issue, transitions, myself), maintaining predictability. No mixed conventions or vague verbs.
With 10 tools, the server is well-scoped for Jira's core functionality. Each tool serves a necessary purpose, covering create, read, update, search, comments, transitions, assignment, and user/project context. No redundancy or bloat.
The set covers the primary Jira workflows: issue lifecycle (create, get, update, transition, assign), search, comments, and context (projects, user). Minor gaps exist (e.g., no delete_issue, no link_issue), but these are not critical for most automation tasks and can be worked around.