MCP Jira Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | Yes | Your Personal Access Token | |
| JIRA_BASE_URL | Yes | The base URL of your self-hosted Jira instance (e.g., https://jira.domain.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
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 has a distinct purpose (add comment vs get comments, create vs update vs delete issue, etc.), so an agent can easily differentiate them without confusion.
All tools follow a consistent 'jira_verb_noun' pattern using snake_case, with verbs like add, assign, create, delete, get, search, update, making naming predictable.
12 tools is well-scoped for a Jira server, covering CRUD operations, comments, assignment, projects, user info, and search without being excessive or too sparse.
Covers essential operations (issue CRUD, comments, assignment, search, projects) but misses issue transitions and linking. Minor gaps that are manageable.