Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your email address associated with the Jira account | |
| JIRA_BASE_URL | Yes | Your Jira Cloud instance URL (e.g., https://your-domain.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
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 |
|---|---|
| get_boardsA | Get all available Jira scrum boards |
| get_issuesB | Get current user's tasks from a specific Jira board |
| get_current_user_infoA | Get current authenticated user information including login, email, timezone |
| search_userB | Search for a user by login name or email |
| get_server_infoA | Get Jira server information including current server time |
| add_comment_to_issueB | Add a comment to a specific Jira issue |
| get_issue_detailB | Get detailed information about a specific Jira issue |
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 7 tools
Each tool targets a distinct resource or action: boards, issues, user info, server info, and comments. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., get_boards, get_issues, add_comment_to_issue. The naming is predictable and clear.
With 7 tools, the set is well-scoped for a Jira server, covering essential operations on boards, issues, users, and server info without being excessive.
The set lacks issue creation, update, and deletion, which are core operations for a Jira server. Agents cannot complete full issue lifecycle tasks, leaving notable gaps.