JIRA MCP Server
by wunderfrucht
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | JIRA instance URL, e.g., https://your-company.atlassian.net | |
| JIRA_TOKEN | No | Token for PAT or Bearer auth | |
| JIRA_PASSWORD | No | Password for Basic auth | |
| JIRA_USERNAME | No | Username for Basic auth | |
| JIRA_AUTH_TYPE | Yes | Authentication type: pat, basic, bearer, or anonymous | |
| JIRA_CACHE_TTL | No | Cache TTL in seconds (default: 300) | 300 |
| JIRA_MAX_RESULTS | No | Max search results (default: 50, max: 200) | 50 |
| JIRA_REQUEST_TIMEOUT | No | Request timeout in seconds (default: 30) | 30 |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues