Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment mode | |
| JIRA_EMAIL | Yes | Your Jira email | |
| JIRA_BASE_URL | Yes | Jira instance URL | |
| JIRA_API_TOKEN | Yes | Jira API token |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_visible_projects | Retrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and basic metadata. |
| jira_get_issue | Retrieve details for a specific Jira issue by key or URL. Use this when the user mentions an issue like "PAYWALL-943" or pastes a Jira link (e.g., https://your.atlassian.net/browse/PAYWALL-943). Returns status, assignee, priority, project, type, labels, components, timestamps, and description. |
| jira_search_issues | Search for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". |
| jira_get_my_issues | Retrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. |
| jira_get_issue_types | Retrieves available issue types. Can get global issue types or project-specific issue types including regular issues and subtasks (Bug, Story, Task, Epic, etc.). |
| jira_get_users | Search for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination. |
| jira_get_priorities | Retrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions. |
| jira_get_statuses | Retrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information. |
| jira_create_issue | Creates a new Jira issue in the specified project. Supports setting issue type, priority, assignee, labels, components, and custom fields. Description accepts plain text and is auto-formatted to ADF: lines ending with ":" become headings, numbered lines create ordered lists, and URLs are linkified. For required custom fields, supply them via customFields (e.g., { "customfield_12345": { id: "..." } }). Returns the created issue with all details. |
| jira_update_issue | Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, and components. Description accepts plain text and is auto-formatted to ADF: headings (lines ending with ":"), numbered/bullet lists, and links. Only specified fields will be updated. |
| jira_add_comment | Adds a comment to an issue. Supports visibility restrictions for groups or roles. Returns the created comment with author details and timestamp. |
| jira_get_project_info | Retrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list. |
| jira_create_subtask | Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. |