Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | Your Jira instance base URL | |
| JIRA_API_TOKEN | Yes | Jira API token (Generate from https://id.atlassian.com/manage-profile/security/api-tokens) | |
| JIRA_USER_EMAIL | Yes | Your Jira account email | |
| JIRA_CURRENT_USER | No | Optional override current user for queries | currentuser() |
| JIRA_TEAM_MEMBERS | No | Optional comma-separated list of team member emails |
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 |
|---|---|
| get_my_issuesB | Get all issues currently assigned to the configured CURRENT_USER |
| add_commentB | Add a comment to a specified Jira issue |
| get_my_work_summaryA | Get a summary of issues the CURRENT_USER has worked on (updated, commented, or transitioned) within a date range |
| get_team_activityB | Get recent issue updates (status changes, comments, assignments) from TEAM_MEMBERS |
| search_issuesA | Search for issues using JQL (Jira Query Language). Use this to find issues by parent/epic, assignee, status, labels, or any other criteria. Example JQL: "parent=TSSE-206", "assignee=currentuser() AND status="In Progress"", "labels=Dec15-19" |
| get_issue_detailsB | Get full details of a specific Jira issue |
| get_project_componentsB | Get all available components for a Jira project |
| update_issue_fieldA | Update a custom field on a Jira issue. Supported fields: Decision Needed, Progress Update, Decision Maker(s), Risks/Blockers, Completion Percentage, Health Status. You can use either the field name or field ID. |
| update_progressA | Update the Progress Update field (customfield_15112) on a Jira issue. This field uses a structured template with three sections:
Options:
|
| create_issueB | Create a new issue in Jira. Supports standard fields (summary, description, assignee, priority, labels) and custom fields (Health Status, Completion Percentage, Progress Update, etc.) |
| get_sprint_tasksA | Retrieve Sprint tasks for the current week or next week. Sprint tasks are tagged with labels in the format MonDD-DD (e.g., Dec15-19 for December 15-19). Two query modes:
The tool automatically calculates the Monday-Friday date range and matches against the corresponding sprint label. |
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/eh24905-wiz/jira-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server