jira-mcp
by skurekjakub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_SITE | Yes | Site host, e.g. your-team.atlassian.net. A scheme and trailing slashes are accepted and stripped | |
| JIRA_EMAIL | Yes | Atlassian account email the API token belongs to | |
| JIRA_CLOUD_ID | Yes | Tenant id | |
| JIRA_API_TOKEN | Yes | API token, from Atlassian account settings | |
| JIRA_ISSUE_KEY | No | Pins jira_add_comment and jira_add_attachment to one issue and drops issueKey from their inputs | |
| JIRA_PROJECT_KEY | Yes | Project jira_create_issue and jira_create_subtask write into | |
| JIRA_ATTACHMENTS_DIR | No | Directory jira_add_attachment reads uploads from. Defaults to /tmp/mcp-attachments | /tmp/mcp-attachments |
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
ActivityMaintained
ResponsivenessNo issues