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 instance URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your 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 |
|---|---|
| get_issue | Get detailed information about a Jira issue by its key or ID |
| create_issue | Create a new Jira issue with specified fields. IMPORTANT: Always use get_create_metadata first to discover required fields, custom fields, and allowed values for the project and issue type. |
| update_issue | Update fields of an existing Jira issue. TIP: Use get_create_metadata to discover available custom fields and their allowed values for the project. |
| assign_issue | Assign a Jira issue to a user |
| search_issues | Search for Jira issues using JQL (Jira Query Language). Returns issue keys and titles. Use get_issue for full details. |
| list_projects | List all accessible Jira projects |
| get_create_metadata | Get field requirements and metadata for creating issues in a project. Shows required fields, custom fields, and allowed values. |
| search_users | Search for Jira users by name or email to get their account ID. Use this to find account IDs for assigning issues. |
| add_comment | Add a comment to a Jira issue |
| get_comments | Get all comments for a Jira issue |
| get_transitions | Get available status transitions for a Jira issue |
| transition_issue | Change the status of a Jira issue by transitioning it |