Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_MCP_URL | Yes | Your Jira instance URL | |
| JIRA_MCP_TOKEN | Yes | API authentication token | |
| JIRA_MCP_TIMEOUT | No | HTTP request timeout in seconds | 30 |
| JIRA_MCP_CACHE_TTL | No | Schema cache TTL in seconds | 3600 |
| JIRA_MCP_VERIFY_SSL | No | Verify SSL certificates | true |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_health_checkA | Verify connectivity to Jira instance and validate authentication. Returns: Connection status and server info including version and URL |
| jira_issue_create_toolA | Create a new Jira issue with automatic custom field validation. The system automatically discovers and validates custom fields based on the project schema. |
| jira_issue_update_toolA | Update an existing Jira issue. Only provided fields are updated. Custom fields are validated against the project schema. |
| jira_issue_get_toolA | Retrieve full details of a single issue including all custom fields. |
| jira_project_get_schemaA | Get field schema for a project and issue type for debugging. This tool helps you understand what fields are available for a project and issue type, including custom fields and their validation rules. |
| jira_search_issues_toolA | Search for Jira issues using multiple criteria. Build a JQL query from the provided criteria and execute it. At least one search criterion must be provided. |
| jira_search_jql_toolA | Execute a JQL (Jira Query Language) query directly. Use this for complex queries that can't be expressed through search_issues criteria. Supports all JQL operators and functions including ORDER BY clauses. |
| jira_filter_create_toolA | Create a new saved filter for reusing complex search queries. Filters allow you to save JQL queries for quick access to frequently-needed issue sets. |
| jira_filter_list_toolA | List all accessible filters. Returns all filters you have permission to view, including your own and shared filters. Returns: List of filter metadata (ID, name, JQL, owner) Example: jira_filter_list_tool() |
| jira_filter_get_toolB | Get complete filter details by ID. |
| jira_filter_execute_toolA | Execute a saved filter and return matching issues. Retrieves the filter's JQL and executes it with pagination support. |
| jira_filter_update_toolA | Update an existing filter. Only provided fields are updated. At least one field must be provided. |
| jira_filter_delete_toolA | Delete a filter. Only the filter owner can delete it. |
| jira_workflow_get_transitions_toolA | Get available workflow transitions for an issue. Returns all transitions available for the issue in its current state, including transition IDs, names, destination statuses, and required fields. |
| jira_workflow_transition_toolB | Transition an issue through workflow. Executes a workflow transition, moving the issue to a new status. Some transitions may require additional fields (e.g., resolution when closing an issue). |
| jira_comment_add_toolA | Add a comment to an issue. Comments support Jira markup for formatting (bold, italic, lists, etc.). |
| jira_comment_list_toolA | List all comments on an issue. Retrieves all comments with author information and timestamps. |
| jira_comment_update_toolA | Update an existing comment. Only the comment author or users with appropriate permissions can update a comment. |
| jira_comment_delete_toolA | Delete a comment. Only the comment author or users with appropriate permissions can delete a comment. |
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
- 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/troylar/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server