MCP Jira Server
by tom28881
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Jira instance URL, e.g., https://your-company.atlassian.net | |
| JIRA_EMAIL | Yes | Your email address associated with the Atlassian account | |
| JIRA_API_TOKEN | Yes | Jira API token generated from Atlassian account settings | |
| JIRA_DEFAULT_PROJECT | No | Default project key for issue creation (optional, e.g., PROJ) | |
| JIRA_FIELD_EPIC_LINK | No | Custom field ID for epic link (optional, auto-detected) | |
| JIRA_FIELD_STORY_POINTS | No | Custom field ID for story points (optional, auto-detected if not set) | |
| AUTO_CREATE_TEST_TICKETS | No | Set to 'true' to automatically create test tickets for stories (optional) | false |
| JIRA_FIELD_ACCEPTANCE_CRITERIA | No | Custom field ID for acceptance criteria (optional) |
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
ResponsivenessSyncing