Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_BASE_URL | Yes | Your Jira base URL, e.g. https://jira.example.com | |
| JIRA_API_TOKEN | Yes | Your Jira API token |
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 |
|---|---|
| get_my_tasksA | Get active tasks assigned to the current user, ordered by priority descending. |
| get_task_detailsA | Get full context for a Jira issue including description, status, assignee, and comments. |
| search_tasksA | Search Jira issues by text query or raw JQL. Provide either 'query' (text search) or 'jql' (raw JQL), not both. |
| update_task_statusB | Transition a Jira issue to a new status using the Jira transitions API. |
| add_commentA | Add a comment to a Jira issue. Supports Markdown formatting. |
| attach_fileA | Upload a file from disk and attach it to a Jira issue. |
| create_taskB | Create a new Jira issue. Description supports Markdown formatting (headings, bold, italic, code, lists, links, blockquotes). |
| update_taskB | Update fields on an existing Jira issue. Only provided fields are changed. Description supports Markdown. |
| link_issuesA | Create a link between two Jira issues. Common link types: Blocks (blocks / is blocked by), Relates (relates to), Duplicate (duplicates / is duplicated by), Cloners (clones / is cloned by). |
| unlink_issuesA | Remove a link between two Jira issues by link ID. Get the link ID from get_task_details issueLinks field. |
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/Eliya-56/MCP-Jira'
If you have feedback or need assistance with the MCP directory API, please join our Discord server