Loading...
This Jira MCP server provides a comprehensive suite of tools for managing Jira issues, sprints, and development information, enabling efficient workflow automation.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This Jira MCP server provides a comprehensive suite of tools for managing Jira issues, sprints, and development information, enabling efficient workflow automation.
This MCP server offers a balance of read and write capabilities for Jira. While the API token authentication provides a basic level of security, careful consideration should be given to the permissions granted to the token and the potential impact of write operations. It is relatively safe for read-only tasks but requires caution when using write operations.
Performance is primarily limited by the Jira API's response times and rate limits. Optimize JQL queries and minimize unnecessary API calls.
Cost is primarily determined by Jira API usage, which may incur charges depending on your Jira plan. Monitor API usage to avoid unexpected costs.
npx @modelcontextprotocol/inspector{
"mcpServers": {
"jira": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-e", "ATLASSIAN_HOST=https://your-company.atlassian.net",
"-e", "ATLASSIAN_EMAIL=your-email@company.com",
"-e", "ATLASSIAN_TOKEN=your-api-token",
"ghcr.io/nguyenvanduocit/jira-mcp:latest"
]
}
}
}ATLASSIAN_HOSTATLASSIAN_TOKENjira_get_issueRetrieves detailed information about a specific Jira issue.
Read-only operation; no data modification.
jira_create_issueCreates a new Jira issue with specified details.
Creates new data; potential for misuse if not properly controlled.
jira_update_issueModifies an existing Jira issue's details.
Modifies existing data; requires careful validation to prevent errors.
jira_search_issueSearches for Jira issues using JQL.
Read-only operation; JQL injection risk mitigated by proper sanitization.
jira_transition_issueTransitions a Jira issue through its workflow.
Changes issue status; potential for workflow disruption if misused.
jira_add_commentAdds a comment to a Jira issue.
Adds data to an issue; potential for spam or inappropriate content.
jira_get_development_informationRetrieves development information (branches, pull requests, commits) linked to a Jira issue.
Read-only operation; no data modification.
jira_link_issuesCreates a link between two Jira issues, defining their relationship.
Creates relationships between issues; potential for incorrect or misleading links.
jira_add_worklogAdds a worklog entry to track time spent on an issue.
Adds data to an issue; potential for inaccurate time tracking.
API Key
local
This MCP server offers a balance of read and write capabilities for Jira. While the API token authentication provides a basic level of security, careful consideration should be given to the permissions granted to the token and the potential impact of write operations. It is relatively safe for read-only tasks but requires caution when using write operations.
Autonomy level depends on the configuration and the specific tools used. Exercise caution when granting write access.
Production Tip
Monitor API usage and error rates to ensure stable performance and prevent abuse.
The MCP server uses API token authentication.
Set the `ATLASSIAN_HOST` environment variable to your Jira instance URL.
No, the server is configured for a single Jira instance.
Create an API token with the minimum required permissions in your Atlassian account.
It should support both, but ensure compatibility with your specific Jira version.
Verify the `ATLASSIAN_HOST`, `ATLASSIAN_EMAIL`, and `ATLASSIAN_TOKEN` environment variables are correctly configured.
Rate limits are imposed by Jira. Monitor API usage to avoid exceeding these limits.