Jira Issue MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_HOST | No | Redis connection string or host:port used for caching tokens. Default: "localhost:6379". | localhost:6379 |
| ELASTIC_URL | No | Elastic endpoint URL. Default: not set. | |
| SERVER_DOMAIN | No | Base URL where this server is reachable (used to build OAuth redirect/callback URLs). Default: "http://localhost:3000". | http://localhost:3000 |
| ELASTIC_API_KEY | No | API key for Elastic (used for telemetry/logging if configured). Default: not set. | |
| ATLASSIAN_CLIENT_ID | Yes | the OAuth client ID from your Atlassian developer app. This and ATLASSIAN_CLIENT_SECRET are mandatory for the OAuth flow to work. | |
| ATLASSIAN_CLIENT_SECRET | Yes | the OAuth client secret from your Atlassian developer app. |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_issueD | Creates an issue to the users |
| get_projectsC | Get the projects the user has access to |
| get_accessible_resourcesC | Fetches a list of resources the user has access to. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| bug_report_prompt | In case of a BUG Issue, please provide the expected result, actual result and steps to reproduce the issue |
| epic_report_prompt | In case of an EPIC Issue, please provide all the details that can help in creating an epic report. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create_issue handles issue creation, get_accessible_resources lists general resources, and get_projects focuses specifically on projects. There is no overlap or ambiguity between these functions.
The naming is mostly consistent with a verb_noun pattern (create_issue, get_projects), but get_accessible_resources uses a more descriptive adjective, slightly deviating from pure verb_noun. Overall, it remains readable and predictable.
With only 3 tools for a Jira server, the count feels too thin for the domain. Jira typically involves CRUD operations on issues, projects, and other resources, so this limited set is insufficient for comprehensive coverage.
The tool surface is significantly incomplete for a Jira server. It includes create_issue but lacks get_issue, update_issue, and delete_issue, and while get_projects is present, other common operations like search_issues or manage_workflows are missing, leading to potential agent failures.