jira-api-mcp-wrapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Email for Jira Cloud account (used with JIRA_API_TOKEN) | |
| JIRA_BASE_URL | No | Jira Cloud instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | No | API token for Jira Cloud (created in Atlassian account settings) | |
| JIRA_BEARER_TOKEN | No | Bearer token for Jira Cloud authentication |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_list_fieldsB | List Jira fields (including customfield_*) from /rest/api/3/field. Use this to map friendly names to field IDs. |
| jira_get_issueA | Fetch a Jira issue by key using /rest/api/3/issue/{key}. You can request specific fields/expand to reduce payload. |
| jira_update_issue_fieldsA | Update Jira issue fields via /rest/api/3/issue/{key} PUT. Supports customfield_* and ADF docs. You must send correct field IDs and value shapes (e.g. user picker needs accountId). |
| jira_search_issues_jqlA | Search issues using JQL via /rest/api/3/search. Returns a page of issues with selected fields. |
| jira_create_issueB | Create an issue via /rest/api/3/issue. Supply fields including project + issuetype and any customfield_* values (including ADF docs). |
| jira_add_commentA | Add a comment to an issue via /rest/api/3/issue/{key}/comment. Body may be plain string or ADF doc object. |
| jira_get_transitionsB | Get available transitions for an issue via /rest/api/3/issue/{key}/transitions. |
| jira_transition_issueA | Transition an issue via /rest/api/3/issue/{key}/transitions. Provide a transition id (use jira_get_transitions first). |
| jira_bulk_create_issuesA | Bulk create issues via POST /rest/api/3/issue/bulk. Provide issueUpdates entries containing fields (and optional update). |
| jira_bulk_get_editable_fieldsB | Get bulk-editable field IDs for a set of issues via GET /rest/api/3/bulk/issues/fields. Use the returned field IDs in selectedActions for jira_bulk_edit_issues. |
| jira_bulk_edit_issuesA | Bulk edit issues via POST /rest/api/3/bulk/issues/fields. You must provide selectedIssueIdsOrKeys, selectedActions (field IDs), and editedFieldsInput. |
| jira_search_usersA | Search users (returns accountId) using /rest/api/3/user/search. Use this to map email/displayName → accountId for user picker fields. |
| jira_resolve_user_account_idA | Resolve a single best-match Jira user and return accountId (for setting user picker custom fields). Uses /rest/api/3/user/search and selects the best candidate. |
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
- 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/jarekbird/jira-api-mcp-wrapper'
If you have feedback or need assistance with the MCP directory API, please join our Discord server