JIRA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Your JIRA instance domain (e.g., company.atlassian.net) | |
| JIRA_USERNAME | Yes | Your JIRA username (usually your email address) | |
| ZAPI_BASE_URL | No | The base URL for the Zephyr API | https://prod-api.zephyr4jiracloud.com/connect |
| JIRA_API_TOKEN | Yes | Your JIRA API token | |
| JIRA_PRODUCT_ID | No | The ID of the product option | |
| ZAPI_ACCESS_KEY | No | Your Zephyr Access Key | |
| ZAPI_SECRET_KEY | No | Your Zephyr Secret Key | |
| JIRA_PROJECT_KEY | Yes | The key for your JIRA project (e.g., SCRUM, DEV, etc.) | |
| JIRA_CRISIS_FIELD | No | The field ID for the crisis field | customfield_10597 |
| JIRA_CRISIS_NO_ID | No | The ID of the 'No' option | 18259 |
| JIRA_CRISIS_YES_ID | No | The ID of the 'Yes' option | 18258 |
| JIRA_PRODUCT_FIELD | No | The field ID for the product field | |
| JIRA_PRODUCT_VALUE | No | The display value for the product | |
| JIRA_CATEGORY_FIELD | No | The field ID for the category field | |
| ZAPI_JWT_EXPIRE_SEC | No | JWT token expiration time in seconds | 3600 |
| JIRA_EPIC_LINK_FIELD | No | The field ID for epic links | customfield_10014 |
| USE_ALTERNATE_CATEGORY | No | Set to 'true' to use alternate category, 'false' for default | |
| JIRA_STORY_POINTS_FIELD | No | The field ID for story points | customfield_10040 |
| AUTO_CREATE_TEST_TICKETS | No | Set to 'true' to automatically create linked Test tickets for Story tickets with points, or 'false' to disable | true |
| JIRA_DEFAULT_CATEGORY_ID | No | The ID of the default category option | |
| JIRA_ALTERNATE_CATEGORY_ID | No | The ID of the alternate category option | |
| JIRA_DEFAULT_CATEGORY_VALUE | No | The display value for the default category | |
| JIRA_ALTERNATE_CATEGORY_VALUE | No | The display value for the alternate category | |
| JIRA_ACCEPTANCE_CRITERIA_FIELD | No | The field ID for acceptance criteria | customfield_10429 |
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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MankowskiNick/jira-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server