Jira MCP server: scoped Jira access for every agent

A useful Jira request is narrower than “organize the backlog.” Name a project, a date window and the fields you need. For example, search unresolved incidents in project OPS, read their owners and priority, then return a shortlist with issue keys. The agent can gather context without changing assignees or workflow state.

For creation, first inspect list_project_issue_types and get_issue_type_fields. Different projects can require different fields. A ticket that sounds complete in prose may still be invalid under the project’s configuration. Have the agent show the intended project, issue type, summary and required values before it calls create_issue.

Moving a ticket to Done is not an edit_issue shortcut. Ask for list_transitions, review the available transition, and approve transition_issue only after the requested state is clear. Jira still decides whether the signed-in user may perform that transition.

Jira MCP server: official Atlassian vs AIPx

Atlassian’s Jira authentication documentation covers the API credential route. The mcp-atlassian repository describes a separate community implementation. AIPx’s Atlassian Rovo integration is another catalog choice; it proxies the official server rather than this REST adapter.

A direct Rovo connection removes an extra gateway from the data path. AIPx is useful when Jira shares an agent with other services or different agents need different tools. It adds another service handling request data and credentials, and it cannot extend Jira project permissions.

Connect Jira to Claude, Claude Code, Cursor or Codex

Use your Jira Cloud site URL, Atlassian email and a personal API token. This adapter does not use the Rovo OAuth connection.

1. Open the AIPx dashboard, choose Jira under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Jira; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Jira

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Jira is the only service you need.

Jira MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Run /mcp and authorize, then ask for project OPS issues opened this week without edits. Inspect the JQL and issue keys before enabling ticket creation. Claude Code MCP setup covers connection scope and reauthorization.

Jira MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

After Cursor signs in, inspect the Jira reads and keep transitions hidden for backlog research. A useful first task is reading one issue by key. The Cursor MCP guide explains project-level configuration.

Jira MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Jira credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

ChatGPT can use the Jira agent endpoint where custom MCP access is available. Ask for a project-bounded issue search first, with writes hidden. See ChatGPT MCP setup for account, client and workspace restrictions.

Scope Jira per agent: reads on Allow, writes on Confirm

For a triage agent, allow search, issue reads and project metadata; hide all four write operations. A delivery assistant can keep reads on Allow and issue creation or comments on Confirm, while transitions remain hidden. These are recommendations for different jobs. The general product defaults are Allow for reads and Confirm for writes.

Confirm depends on the client’s approval behavior. It is not a gateway pause that guarantees a human review. If an agent must never change ticket state, set transition_issue to Hide. Hidden tools cannot be called by that agent. See MCP access control for this boundary.

Use Jira and Confluence in one agent

Connect Confluence separately to compare the specification with the issue’s acceptance criteria. Read the page and ticket first, then produce a proposed comment containing source links. Keep Confluence page updates hidden if the task is Jira triage. A combined context request does not need combined write authority.

For teams evaluating a different tracker, Linear MCP offers a separate issue surface. Repository evidence can come from GitHub, while Sentry can provide the error that motivated the ticket. Choose the account explicitly when more than one Jira site is connected.

Jira Cloud limits and workflow checks

This connector supports Jira Cloud. Do not configure a Data Center URL expecting the same adapter to work. Search results are bounded; ask the agent to state the JQL and any pagination or result limit so an incomplete list is not mistaken for the whole backlog.

API token access remains limited by the authenticated Jira account. AIPx rules restrict callable tools, not individual projects inside a Jira account. Use an appropriately limited Jira user when project isolation matters. Authentication errors, required-field errors and unavailable transitions need a corrected request or provider permission, rather than another broad prompt.

Browse all MCP integrations to choose another connection for this agent.

The Jira connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.