jiri-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Your Jira Cloud URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_API_TOKEN | Yes | API token from Atlassian API Tokens |
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 (Jira Query Language). Returns a summary table of matching issues. Example JQL: 'project = PROJ AND status = "In Progress" ORDER BY updated DESC' |
| get_issueA | Get full details of a single Jira issue by its key (e.g., PROJ-123). Returns summary, status, description, comments, and metadata. |
| create_issueA | Create a new Jira issue. Requires project key, summary, and issue type. Optionally set description, assignee, labels, and priority. |
| update_issueA | Update fields on an existing Jira issue. Only the provided fields will be changed; others remain untouched. |
| add_commentB | Add a comment to a Jira issue. |
| list_transitionsA | List available status transitions for a Jira issue. Use this to discover valid transition IDs before calling transition_issue. |
| transition_issueA | Transition a Jira issue to a new status. Use list_transitions first to get valid transition IDs. |
| assign_issueA | Assign a Jira issue to a user by their account ID. Use search_users to find a user's account ID. Pass an empty accountId to unassign. |
| list_projectsA | List all Jira projects accessible to the authenticated user. |
| search_usersA | Search for Jira users by name or email. Returns account IDs which can be used for assignment. |
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/chatchawarn035/jira-mcp-type-script'
If you have feedback or need assistance with the MCP directory API, please join our Discord server