Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAT | Yes | Your Personal Access Token for Jira authentication | |
| JIRA_BASE_URL | Yes | The base URL of your self-hosted Jira instance (e.g., https://your-jira-instance.com/) |
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 |
|---|---|
| jira_get_issueC | Get details of a Jira issue by its key |
| jira_search_issuesC | Search for Jira issues using JQL |
| jira_create_issueC | Create a new Jira issue |
| jira_update_issueC | Update an existing Jira issue |
| jira_delete_issueC | Delete a Jira issue |
| jira_assign_issueC | Assign or unassign a Jira issue |
| jira_get_commentsC | Get comments on a Jira issue |
| jira_add_commentC | Add a comment to a Jira issue |
| jira_get_transitionsC | Get available transitions for a Jira issue |
| jira_transition_issueC | Transition a Jira issue to a new status |
| jira_get_projectsB | Get all Jira projects |
| jira_get_projectA | Get details of a specific Jira project |
| jira_search_usersC | Search for Jira users |
| jira_get_current_userB | Get the current authenticated user |
| jira_link_issuesC | Link two Jira issues |
| jira_add_watcherC | Add a watcher to a Jira issue |
| jira_get_prioritiesB | Get all available priorities |
| jira_get_statusesB | Get all available statuses |
| jira_get_create_metaA | Get metadata for creating issues - shows required fields and allowed values (dropdown options) for a project and issue type. IMPORTANT: Call this before creating an issue to know what fields are required and what values are allowed. |
| jira_get_edit_metaB | Get metadata for editing an issue - shows editable fields and allowed values for an existing issue |
| jira_get_project_versionsA | Get all versions for a project - use this to find valid values for fixVersions and affectsVersions fields |
| jira_get_project_componentsA | Get all components for a project - use this to find valid values for the components field |
| jira_get_fieldsB | Get all available fields including custom fields - shows field IDs, names, and types |
| jira_get_field_optionsB | Get allowed values/options for a specific field in a project and issue type context |
| jira_get_issue_link_typesB | Get all available issue link types |
| jira_create_issue_advancedA | Create a new Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_create_meta first to discover required fields and allowed values. |
| jira_update_issue_advancedA | Update a Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_edit_meta first to discover editable fields and allowed values. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jira Configuration | Current Jira server configuration |
TDQS
Scored across 27 tools
Most tools have distinct purposes targeting specific Jira resources and actions, but there is some overlap between jira_create_issue/jira_create_issue_advanced and jira_update_issue/jira_update_issue_advanced, which could cause confusion about when to use the advanced versions. The descriptions help clarify that advanced versions support more fields, but the distinction might not be immediately obvious to an agent.
All tools follow a consistent jira_verb_noun pattern with snake_case, making them predictable and easy to parse. The naming convention is uniform across all 27 tools, with no deviations in style or structure.
With 27 tools, the count is on the high side for a typical MCP server, bordering on heavy. While Jira is a complex system with many operations, some tools like jira_get_priorities or jira_get_statuses might be considered auxiliary, potentially making the set feel bloated compared to more streamlined servers.
The tool set provides comprehensive coverage for Jira operations, including full CRUD for issues (create, get, update, delete), metadata discovery (get_create_meta, get_edit_meta), search capabilities, user and project management, and workflow actions like transitions and linking. There are no obvious gaps, and the advanced tools ensure support for custom fields and complex scenarios.