Connect Jira to Allin with MCP
Everything to prepare to connect this tool to Allin.
This guide is public. It contains no company configuration and grants no Allin access. Share secrets through your usual secure channel.
Technical preparation
- 1
Use an Atlassian account with access to your Jira Cloud site. This connector does not support Jira Server or Data Center.
- 2
If your organization restricts MCP clients, ask an Atlassian administrator to allow the Allin callback domain in Atlassian MCP settings. Also check any IP restrictions.
- 3
Save the connection, then click Authorize. Sign in to Atlassian and select the site and access you need. No manual Client ID or Client Secret setup.
- 4
Alternative without OAuth: in Atlassian Administration → Rovo → Rovo MCP server → Authentication, enable API token authentication. Then create a token with the required scopes at https://id.atlassian.com/manage-profile/security/api-tokens.
- 5
In Allin, select Atlassian personal API token and enter the account email and token. For a service account key, select the matching mode and enter only the key. Both modes use a shared account for authorized tools; individual Allin accounts require OAuth.
- 6
In API mode, available tools depend on token scopes and some calls require the site cloudId. Atlassian IP restrictions still apply.
- 7
Discover the tools, then allow only those you need in Allin. Atlassian MCP may also offer Confluence and other product tools depending on the account permissions.
- 8
In personal mode, each member connects their own account from My connections. In shared mode, calls use the permissions of the Atlassian account connected by the administrator.
- 9
Some Atlassian search and context tools consume Rovo credits. Check your plan limits and costs before using them.
What to give the Allin administrator
An Atlassian account authorized on the Jira Cloud site, via OAuth or an API token. Enter secrets only in the Allin connection form, never in this shareable guide.
MCP server address
https://mcp.atlassian.com/v2/mcp?tools=allIf the connection fails
If consent is rejected, check the allowed callback domain, IP restrictions and site permissions. Keep tools=all so Allin can manage permissions per tool. The legacy /v1/sse endpoint is no longer supported.
Next, in Allin
Save the connection, authorize the account if needed, then discover tools. Enable only the tools you need and grant access to the relevant teams or people.
Open setup in Allin