Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_TOKEN | No | API token or Personal Access Token | |
| JIRA_PASSWORD | No | Password for basic auth | |
| JIRA_USERNAME | No | Username for basic auth or email for Jira Cloud | |
| JIRA_SERVER_URL | No | URL of your Jira server | |
| JIRA_AUTH_METHOD | No | Authentication method ('basic_auth' or 'token_auth') |
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_jira_projectsB | Get all accessible Jira projects |
| get_jira_issueC | Get details for a specific Jira issue by key |
| search_jira_issuesC | Search for Jira issues using JQL (Jira Query Language) |
| create_jira_issueC | Create a new Jira issue. Common issue types include 'Bug', 'Task', 'Story', 'Epic' (capitalization handled automatically) |
| create_jira_issuesC | Bulk create new Jira issues. IMPORTANT: For 'issue_type', use the exact case-sensitive types in your Jira instance (common: 'Bug', 'Task', 'Story', 'Epic') |
| add_jira_commentC | Add a comment to a Jira issue |
| get_jira_transitionsC | Get available workflow transitions for a Jira issue |
| transition_jira_issueC | Transition a Jira issue to a new status |
| get_jira_project_issue_typesB | Get all available issue types for a specific Jira project |
| create_jira_projectC | Create a new Jira project |
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
Every tool has a clearly distinct purpose targeting specific Jira resources and actions. The tools cover different operations like creation, retrieval, searching, and transitions without overlap, making it easy for an agent to select the right tool for each task.
All tool names follow a consistent verb_noun pattern with 'jira' as a prefix (e.g., create_jira_issue, get_jira_projects). The naming is uniform across all tools, using snake_case and clear action verbs, which enhances predictability and readability.
With 10 tools, this server is well-scoped for Jira operations, covering core functionalities like issue management, project handling, and workflow transitions. Each tool serves a specific purpose without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive coverage for key Jira workflows, including CRUD operations for issues and projects, searching, and transitions. A minor gap is the lack of tools for updating or deleting issues or projects, which agents might need to work around, but core operations are well-covered.