jira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Atlassian site URL, e.g. https://myteam.atlassian.net | |
| JIRA_EMAIL | Yes | Atlassian account email (basic-auth pair with token) | |
| JIRA_TOKEN | Yes | API token from id.atlassian.com | |
| MCP_JIRA_BRIEF_MAX | No | Max length of <brief> summary on issue descriptions. 0 disables enforcement | 100 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_versionA | Get the Jira MCP server version and service status. |
| jira_writeA | Create or update Jira resources (non-destructive). Call with operation="help" to list all available write operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_write(operation="CreateIssue", params={"project_key": "PROJ", "issue_type": "Task", "summary": "Fix login bug"}) |
| jira_executeA | Trigger Jira state changes (transition, assign, unassign). Distinct from write because these are side-effects on existing issues rather than resource creation. Call with operation="help" to list all available execute operations. Example: jira_execute(operation="TransitionIssue", params={"issue_key": "PROJ-1", "transition_id": "31"}) |
| jira_deleteA | Delete Jira resources (destructive, irreversible). Call with operation="help" to list all available delete operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_delete(operation="DeleteIssue", params={"issue_key": "PROJ-123"}) |
| jira_readA | Query Jira data (safe, read-only). Call with operation="help" to list all available read operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_read(operation="SearchIssues", params={"jql": "project = PROJ AND status = Open"}) |
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/nikitatsym/jira-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server