Loading...
This MCP server provides tools to interact with Jira, enabling ticket management, JQL queries, and project listing, secured by API key authentication.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server provides tools to interact with Jira, enabling ticket management, JQL queries, and project listing, secured by API key authentication.
This server offers useful Jira interaction tools but requires careful API key management. It's safe for read operations and controlled ticket creation, but risky for deletion or modification without proper authorization and monitoring.
Performance depends on the Jira instance's responsiveness and network latency. JQL queries with large result sets may take longer to execute.
Cost depends on Jira API usage, which may be subject to rate limits or usage-based pricing. Consider optimizing JQL queries and limiting the number of results returned.
npm install
```{
"mcpServers": {
"Jira communication server": {
"command": "node",
"args": ["/PATH_TO_THE_PROJECT/build/index.js"],
"env": {
"JIRA_URL": "https://XXXXXXXX.atlassian.net",
"JIRA_API_MAIL": "Your email",
"JIRA_API_KEY": "KEY_FROM : https://id.atlassian.com/manage-profile/security/api-tokens"
}
}
}
}KEY_FROMexecute_jqlExecutes a JQL query and returns the results.
Read-only operation that retrieves data based on the query.
get_only_ticket_name_and_descriptionFetches the name and description of a Jira ticket.
Read-only operation that retrieves specific ticket information.
create_ticketCreates a new Jira ticket with specified parameters.
Creates a new ticket, which is a non-destructive write operation.
list_projectsLists available Jira projects.
Read-only operation that retrieves project information.
delete_ticketDeletes a Jira ticket based on its ID or key.
Deletes a ticket, which is a destructive operation.
edit_ticketModifies an existing Jira ticket.
Modifies ticket details, potentially altering important data.
get_all_statusesRetrieves all available statuses in Jira.
Read-only operation that retrieves status information.
assign_ticketAssigns a Jira ticket to a specified user.
Assigns a ticket, which is a non-destructive write operation.
query_assignableFinds users assignable to a project.
Read-only operation that retrieves user information.
add_attachment_from_public_urlAdds an attachment to a ticket from a public URL.
Adds an attachment, which is a non-destructive write operation.
add_attachment_from_confluenceAdds an attachment from a Confluence page to a ticket.
Adds an attachment, which is a non-destructive write operation.
API Key
local
This server offers useful Jira interaction tools but requires careful API key management. It's safe for read operations and controlled ticket creation, but risky for deletion or modification without proper authorization and monitoring.
Autonomy depends on the configured permissions of the Jira API key. Exercise caution when granting access to destructive tools like 'delete_ticket'.
Production Tip
Monitor API usage to prevent exceeding Jira API rate limits and implement robust error handling to gracefully handle API failures.
Store the API key securely using environment variables or a secrets management system. Avoid hardcoding the key in your code.
The server will likely return an error. Implement retry logic with exponential backoff to handle rate limiting.
Potentially, but it depends on the specific API endpoints and permissions required for Service Management. Test thoroughly.
Use the MCP Inspector or add custom logging to track API requests and responses.
It likely supports both, but ensure the JIRA_URL is correctly configured for your Jira instance.
Implement error handling to catch API errors and provide informative messages to the user.
You may need to configure Jira to allow larger attachments or use a different method for uploading large files.