JIRA MCP Server
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 | |
| JIRA_SCOPES | No | Comma-separated list of permission scopes to restrict available tools (e.g., boards:read,sprints:read,issues:read) | |
| JIRA_BASE_URL | Yes | The base URL of your JIRA instance (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your JIRA API token | |
| JIRA_ALLOWED_BOARDS | No | Pipe-separated list of board IDs or names to restrict access (e.g., 123|My Board) | |
| JIRA_ALLOWED_PROJECTS | No | Pipe-separated list of project keys to restrict access (e.g., PROJ|DEV) | |
| JIRA_ALLOWED_ISSUE_TYPES | No | Pipe-separated list of issue types to restrict access (e.g., Bug|Task|Story) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_list_boardsA | List all accessible JIRA boards. Returns board IDs, names, types (scrum/kanban), and project keys. |
| jira_get_active_sprintA | Get the currently active sprint for a specific board. Returns sprint ID, name, dates, and goal. |
| jira_list_sprintsB | List sprints for a board or project. Returns sprint IDs, names, states, dates, and goals sorted by most recent first. Supports pagination. |
| jira_get_sprint_issuesA | Get all issues in a specific sprint. Returns issue keys, summaries, statuses, and assignees by default. Use the fields parameter to customize which fields are returned. |
| jira_get_my_sprint_issuesA | Get issues assigned to the current user in a specific sprint. Filters by assignee = currentUser(). Returns issue keys, summaries, statuses, and priorities sorted by status then priority by default. Use the fields parameter to customize which fields are returned. |
| jira_get_issueA | Get detailed information about a specific JIRA issue by its key (e.g., PROJ-123). Returns all fields by default including custom fields. Use the fields parameter to reduce response size. |
| jira_search_issuesA | Search for issues using JQL (JIRA Query Language). Returns up to 50 issues by default. IMPORTANT: Queries must be bounded with a project filter or other restriction (e.g., assignee, sprint) - unbounded queries are rejected by JIRA. Example: "project = PROJ AND status = "In Progress"" |
| jira_get_backlog_statsA | Get aggregated statistics for issues matching a JQL query. Returns counts grouped by status, type, priority, and assignee by default. Supports custom pivoting on any field pair with aggregation actions (count, sum, avg, cardinality) and flexible field filters. |
| jira_get_sprint_reportA | Generate a sprint report for retrospectives. Returns issue counts and story points grouped by status categories, bug metrics, and label-specific tracking. Compares current sprint with previous sprint. |
| jira_get_issue_commentsB | Get comments on a specific JIRA issue. Returns comment author, body, and creation date. |
| jira_update_issueA | Update fields on a JIRA issue. Can update summary, description, assignee, priority, labels, and custom fields. |
| jira_get_transitionsA | Get available status transitions for an issue. Use this to see what statuses an issue can be moved to. |
| jira_get_issue_historyA | Get the changelog/history of a JIRA issue. Returns all field changes, status transitions, and other modifications. |
| jira_transition_issueA | Transition an issue to a new status. Use jira_get_transitions first to get valid transition IDs. |
| jira_add_commentB | Add a comment to a JIRA issue. |
| jira_create_issueA | Create a new JIRA issue. Returns the created issue key and ID. |
| jira_list_attachmentsA | List all attachments on a JIRA issue. Returns attachment IDs, filenames, sizes, and types. |
| jira_download_attachmentA | Download an attachment from JIRA to a local file path. |
| jira_upload_attachmentB | Upload a file as an attachment to a JIRA issue. |
| jira_get_field_schemaA | Get available JIRA fields with their IDs, names, and types. Useful for discovering custom field IDs (e.g., finding the ID for "Story Points" to use in stats aggregations). Returns field metadata including schema type. |
| jira_get_create_fieldsA | IMPORTANT: Call this BEFORE creating an issue to discover required fields and their formats. Returns all required fields for a project and issue type, including custom fields, with allowed values and format hints. This prevents "field is required" errors during issue creation. |
| jira_list_field_valuesA | List discrete values for a JIRA field. Supports labels, priorities, statuses, issue types, resolutions, and components. Useful for discovering valid values before creating/updating issues. |
| jira_search_usersA | Search for JIRA users by name, email, or display name. Returns accountId which can be used for mentions or assignments. |
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/SuppleAardvark/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server