Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_BASE_URL | Yes | Your Jira instance URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your Jira 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueB | Get detailed information about a Jira issue by its key or ID |
| create_issueA | Create a new Jira issue with specified fields. IMPORTANT: Always use get_create_metadata first to discover required fields, custom fields, and allowed values for the project and issue type. |
| update_issueB | Update fields of an existing Jira issue. TIP: Use get_create_metadata to discover available custom fields and their allowed values for the project. |
| assign_issueC | Assign a Jira issue to a user |
| search_issuesA | Search for Jira issues using JQL (Jira Query Language). Returns issue keys and titles. Use get_issue for full details. |
| list_projectsB | List all accessible Jira projects |
| get_create_metadataB | Get field requirements and metadata for creating issues in a project. Shows required fields, custom fields, and allowed values. |
| search_usersA | Search for Jira users by name or email to get their account ID. Use this to find account IDs for assigning issues. |
| add_commentC | Add a comment to a Jira issue |
| get_commentsC | Get all comments for a Jira issue |
| get_transitionsC | Get available status transitions for a Jira issue |
| transition_issueC | Change the status of a Jira issue by transitioning it |
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 12 tools
Each tool has a clearly distinct purpose targeting specific Jira operations like issue management, metadata retrieval, or user search. The descriptions reinforce this separation, such as distinguishing search_issues (returns keys/titles) from get_issue (full details), preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case (e.g., create_issue, get_comments, list_projects). The naming is predictable and readable throughout, with no deviations in style or convention.
With 12 tools, this server is well-scoped for Jira operations, covering core workflows like issue CRUD, commenting, transitions, and metadata. Each tool earns its place without bloat, aligning with typical domain needs.
The toolset provides complete coverage for Jira issue lifecycle management, including create, read, update, assign, transition, and comment operations. It also supports essential metadata and user search, leaving no obvious gaps for agent workflows.