Jira
The Jira connector allows AI agents to query projects, search issues using JQL, create and update issues, add comments, and transition issue statuses — all through the Atlassian Cloud REST API using OAuth 2.0. Your credentials are stored encrypted in MCPGate's vault and are never exposed to the AI client.
Atlassian Cloud only
yourcompany.atlassian.net). Self-hosted Jira Data Center is not currently supported.Tool reference#
The Jira connector exposes 8 tools: 4 read and 4 write.
| Tool | Category | Description |
|---|---|---|
| jira_list_projects | read | List Jira projects |
| jira_search_issues | read | Search issues with JQL |
| jira_get_issue | read | Get issue details |
| jira_list_boards | read | List Jira boards |
| jira_create_issue | write | Create a new issue |
| jira_update_issue | write | Update issue fields |
| jira_add_comment | write | Add comment to issue |
| jira_transition_issue | write | Change issue status |
Common guardrail recipes#
Read-only access#
Enable only jira_list_projects, jira_search_issues, jira_get_issue, and jira_list_boards. Deny all write tools. Useful for reporting agents that summarise sprint progress or surface blocked issues.
Restrict to specific projects#
Apply the allow_values template to jira_create_issue and target the project_key field. Provide a list of allowed project keys (e.g. ENG, OPS). The AI will be denied if it attempts to create issues in any other project.
Block status transitions#
Deny jira_transition_issue while keeping read and comment tools enabled. This prevents the AI from moving issues through the workflow — useful when humans should own status changes.
Troubleshooting#
- JQL syntax errors —
jira_search_issuesuses Jira Query Language. Ensure the AI is constructing valid JQL (e.g.project = ENG AND status = "In Progress"). Invalid JQL returns a 400 error. - Transition ID required —
jira_transition_issuerequires atransition_id, not a status name. Use the Jira REST API orjira_get_issueto discover available transition IDs for an issue first. - Permission denied on a project — The connected Atlassian account must have Browse Project permission for the target project. Check project permissions in your Jira instance settings.