Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your email (Cloud) or username (Server) | |
| JIRA_BASE_URL | Yes | Your Jira site URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_API_TOKEN | Yes | API token (Cloud) or Personal Access Token (Server) | |
| JIRA_AUTH_TYPE | Yes | Authentication type: 'cloud' or 'server' |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_issuesA | Search Jira issues using JQL. Returns key, summary, status, assignee, priority, and type. |
| get_issueA | Get full details of a single Jira issue by its key (e.g. PROJ-123). |
| create_issueB | Create a new Jira issue in a project. |
| update_issueB | Update fields on an existing Jira issue. |
| add_commentC | Add a comment to a Jira issue. |
| get_transitionsA | Get available status transitions for an issue (useful before transitioning). |
| transition_issueA | Transition a Jira issue to a new status. Use get_transitions first to find the right transition ID. |
| assign_issueA | Assign a Jira issue to a user. For Cloud use accountId, for Server use username. |
| list_projectsA | List all Jira projects accessible to the authenticated user. |
| get_myselfA | Get the profile of the currently authenticated Jira user. |
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/ashu-arora/Jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server