MCP Jira Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | No | Personal Access Token. Used only when JIRA_COOKIE is not set. | |
| JIRA_COOKIE | No | Full HTTP Cookie header value from an authorized browser session. If both JIRA_COOKIE and JIRA_PAT are set, this takes precedence. | |
| JIRA_BASE_URL | Yes | Base URL of the Jira instance, e.g. https://jira.example.com | |
| JIRA_USER_AGENT | No | Optional custom User-Agent for requests. |
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_get_issueA | Get details of a specific Jira issue by its key (e.g., PROJ-123) |
| jira_search_issuesA | Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() AND status != Done" |
| jira_create_issueB | Create a new Jira issue in a specified project |
| jira_update_issueC | Update an existing Jira issue |
| jira_add_commentB | Add a comment to a Jira issue |
| jira_get_commentsB | Get all comments from a Jira issue |
| jira_get_projectsA | List all available Jira projects |
| jira_get_projectA | Get details of a specific Jira project |
| jira_get_issue_typesA | Get available issue types for a project |
| jira_assign_issueB | Assign a Jira issue to a user |
| jira_delete_issueA | Delete a Jira issue permanently |
| jira_get_current_userA | Get information about the currently authenticated 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 12 tools
Each tool targets a distinct resource and action: issues, projects, comments, users, and issue types are clearly separated. There is no overlap between search/get/create/update/delete operations, making misselection unlikely.
All tool names follow the consistent pattern jira_<verb>_<noun> using snake_case. The verbs are standard and predictable, such as get, create, update, delete, search, add, and assign, with no mixed conventions.
12 tools is a well-scoped count for a Jira integration, covering core issue, project, and comment workflows without unnecessary bloat. Each tool serves a clear purpose within the domain.
The surface covers issue CRUD, searching, comments, project lookup, assignment, and user info, which handles common workflows well. A notable gap is the absence of issue transition/status-change functionality, which is core to Jira usage, though agents can work around it with update_issue in some cases.