Trying to connect Atlassian Rovo MCP to Gemini AI

Manohar Kurapati

Hi

I am new to the community. At my company, we are trying to connect Bitbucket to Google Gemini via Atlassian Rovo MCP. Since there is no direct connector, we have to set up a custom MCP server. The form requires many fields to be filled. The Atlassian documentation doesn't clearly explain how to get these details. Please, can someone who has tried this guide me on how to get these details? Thanks

Theresa Garritano

Hi @Manohar Kurapati

To connect Google Gemini to Bitbucket (and other Atlassian Cloud products) via the Atlassian Rovo MCP Server, you need to configure OAuth 2.1 details that are registered specifically for MCP's agent interface.

The reason standard Atlassian Developer Console apps often fail here is that Atlassian Rovo MCP requires specialized agent-interface scopes that use Dynamic Client Registration (DCR) to generate your Client ID and Client Secret.

Here is the step-by-step breakdown of how to obtain each value and fill out your form:

1. Generate Your Client ID and Client Secret

1. In Gemini's MCP configuration screen, find and copy the Redirect / Callback URI (e.g., https://.../oauth/callback).
2. Run the following Dynamic Client Registration (DCR) request in your terminal, replacing <GEMINI_REDIRECT_URI> with the callback URL copied from Gemini:

curl -X POST 'https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3/dcr/register' \ -H 'Content-Type: application/json' \ -d '{ "client_name": "Gemini Enterprise MCP Client", "redirect_uris": ["<GEMINI_REDIRECT_URI>"], "grant_types": ["authorization_code", "refresh_token"], "response_types": ["code"], "token_endpoint_auth_method": "client_secret_basic" }'

1. The JSON response will return a client_id and client_secret. Copy these into the form.

2. Form Field Values

Field	Value to Enter	Notes
Authentication Method	OAuth 2.0	(Already selected)
MCP Server URL *	https://mcp.atlassian.com/v2/mcp	The MCP v2 endpoint
Authorization URL *	https://auth.atlassian.com/authorize	Atlassian OAuth authorization endpoint
Authorization URL Parameters	&response_type=code&prompt=consent	Enforces consent prompt. Do not include an audience parameter
Token URL *	https://auth.atlassian.com/oauth/token	Token exchange endpoint
Client ID *	<client_id from Step 1>	From your DCR curl response
Client Secret	<client_secret from Step 1>	From your DCR curl response
Scopes	(See below)	Space-separated list of scopes
Enable PKCE Support	Optional / Checked if required	Atlassian OAuth 2.1 supports PKCE
Use HTTP Basic Authentication	Checked	Required since DCR uses client_secret_basic

3. Required Scopes

For Bitbucket operations via Atlassian MCP v2, enter the following space-separated string into the Scopes field:

read:me read:account offline_access read:bitbucket:agent-interface write:bitbucket:agent-interface

(If you only need read-only access to Bitbucket, you can omit write:bitbucket:agent-interface.)

Tip: If your team also wants Gemini to interact with Jira or Confluence via the same MCP server, you can include those scopes as well:

read:jira:agent-interface search:jira:agent-interface read:confluence:agent-interface search:confluence:agent-interface

4. Verify and Complete

1. Click Verify Auth.
2. A browser window will open prompting you to log in to your Atlassian account and select your workspace/site to grant consent.
3. Once consent is granted, the MCP connection will be active and Gemini will be able to discover and run Bitbucket tools (reading repositories, viewing pull requests, checking pipelines, etc.).

Let me know if that helps!