Jira MCP Server
by stolostron
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your email address associated with the Atlassian account (required for Cloud authentication) | |
| JIRA_TEAMS | No | JSON object mapping team names to arrays of usernames (e.g., {"frontend": ["alice", "bob"]}) | |
| JIRA_TIMEOUT | No | Timeout in seconds for Jira API requests (default: 30) | 30 |
| JIRA_SERVER_URL | Yes | The URL of the Jira server (e.g., https://your-company.atlassian.net) | |
| JIRA_VERIFY_SSL | No | Whether to verify SSL certificate (default: true) | true |
| JIRA_MAX_RESULTS | No | Maximum number of results to return from Jira (default: 100) | 100 |
| JIRA_ACCESS_TOKEN | Yes | Your personal access token for Jira authentication | |
| JIRA_COMPONENT_ALIASES | No | JSON object mapping aliases to actual component names (e.g., {"ui": "User Interface"}) |
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
ActivityActive
ResponsivenessNo issues