This MCP server for Jira utilizes Atlassian's scoped API tokens, allowing for secure interactions with Jira's API through the modern `api.atlassian.com` gateway.
From the registry: Jira MCP server with scoped API tokens via api.atlassian.com gateway
Please install the `mcp-jira-scoped` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Create scoped Atlassian API token** — Go to Atlassian API Tokens page, click 'Create API token with scopes', grant read:jira-work and optionally write:jira-work, read:jira-user, read:me (https://id.atlassian.com/manage-profile/security/api-tokens)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","mcp-jira-scoped"]
- required environment variables:
- `JIRA_INSTANCE`: Instance name (e.g. 'mycompany' for mycompany.atlassian.net) (example: `yourcompany`)
- `JIRA_USER_EMAIL`: Email associated with the token (example: `[email protected]`)
- `JIRA_API_TOKEN`: Scoped API token (ATATT prefix) (example: `<your-scoped-token>`)
- optional environment variables:
- `JIRA_SCOPES`: Comma-separated scopes. Defaults to read:jira-work (read-only) (example: `read:jira-work,write:jira-work`)
- `JIRA_CLOUD_ID`: Atlassian Cloud ID. Auto-fetched if not set
Note: Uses modern scoped Atlassian API tokens via api.atlassian.com gateway.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.JIRA_INSTANCErequiredInstance name (e.g. `mycompany` for `mycompany.atlassian.net`).JIRA_API_TOKENrequiredScoped API token (`ATATT...` prefix).JIRA_USER_EMAILrequiredEmail associated with the token.Atlassian Rovo MCP Server