Setting up ChatGPT (OpenAI) MCP Server with Atlassian Rovo (Atlassian AI)

[Gaia Tamir Azran]

hi, im trying to Set up ChatGPT (OpenAI) MCP Server with Atlassian Rovo (Atlassian AI) by this doc - https://support.atlassian.com/atlassian-rovo-mcp-server/docs/setting-up-chatgpt/

for that, i want to create a service account in jira 'service account'. will it work? also, i need to choose the scopes after creating the service account after choosing 'OAuth 2.0'. in the doc they dont say which scopes i need for the gpt connection. and there are 438! scopes. please assist firstly, if this type of user will work for me, and secondly, what scoped to choose.

[Peter_DevSamurai]

Hi @Gaia Tamir Azran , 

Your method for a dedicated service account is what Atlassian recommends for Chatgpt MCP integration. You just need to make sure that this service user has browse permission on the projects/spaces you want ChatGPT to access. You can try the steps below to setup the service account with OAuth 2.0:

• Create the service account

  • admin.atlassian.com → Directory → Users → Invite user
  • Use an email you control (ex: your company's shared mailbox).
  • Add the user to the groups that give read access to the Jira projects and Confluence spaces you want indexed.
    
    

• Register the OAuth app (once per org)

  • Go to https://developer.atlassian.com/console/myapps/ → Create app → OAuth 2.0 (authorization code)
  • Callback URL: https://chat.openai.com/aip/YOUR_PLUGIN_ID/oauth/callback (copy the exact URL from the ChatGPT plugin install page -> Itt’s shown when you click “Install an unverified plugin” or “Develop your own plugin”).
    
    

• Scopes you actually need (these are the ones Atlassian and OpenAI use for ChatGPT ↔ Rovo MCP):, you only need like 6-7 below scopes, and won't be needing all 438.

  • offline_access : Required for refresh tokens

  • read:me : Identify the service user

  • read:jira-work : Read issues, projects, boards, filters
  • read:jira-user : Read user details (for @mentions etc.)
  • read:confluence-content.all : Read all Confluence pages/spaces (or restrict to specific spaces if you prefer granular scopes :) )

  • read:confluence-space : Space-level read (if you use granular instead of .all)

  • read:confluence-props : Read page properties
  • #Note: If you want to be more restrictive (which is recommended for production), replace read:confluence-content.all with the granular space scopes for only the spaces you want indexed (ex: read:confluence-content:SPACEKEY).
    
    
• Install the ChatGPT plugin
  • In ChatGPT → Plugins → Develop your own → follow the wizard.
  • Paste your OAuth Client ID and Secret when asked.
  • The first connection will ask the service account to consent – log in as the service account (or pre-consent as site admin if possible).

  • After this =>  The MCP server will be able to pull Jira issues and Confluence pages into ChatGPT securely.

You can refer to the below links:

• ChatGPT + Rovo MCP guide 
• Recommended Atlassian scopes

I hope everything works out well for you!

Best,

Peter

[Gaia Tamir Azran]

hi @Peter_DevSamurai i tried but keep getting 'internal server error' i established an app in atlassian developer and gave all required scopes

BTW your chatgpt flow is the old one- now its apps&connectors not plugins, so the url should be https://chatgpt.com/connector_platform_oauth_redirect

i think i did everything as excepted but something is not working for me.

[Peter_DevSamurai]

Hi @Gaia Tamir Azran , 

Thank you for the update and I'll note this down! The "internal server error" is likely tied to this mismatch or a scope/consent hiccup during the connector setup. 

As corrected, change the OAuth Redirect URI to: https://chatgpt.com/connector_platform_oauth_redirect; besides this everything should still remain. If the error persists, can you share the error payload or screenshot. What's your Chatgpt plan -> This may affect the connector limits.  

[Gaia Tamir Azran]

our chatgpt plan is enterprise 

here is the screenshot i get. nothing else

attached screenshot of the app i created in jira developer:

[Peter_DevSamurai]

Hi @Gaia Tamir Azran ,

ChatGPT enterprise requires workspace admin approval for full MCP. YOu can check:
1) Re-verify scopes:

• Your scopes look good, can you help me ensure the below are included: offline_access (for refresh), read:jira-work, read:confluence-content.all (or granular like read:confluence-content:SPACEKEY), and read:me.
• Note: Workspace admins must approve scopes in ChatGPT settings > Workspace > Connectors > Enable for your app (under "Custom connectors").

2) Re-Authorize the Connector:

• In ChatGPT: Settings > Workspace (as admin) > Connectors/Apps > Your "SVC-ChatGPT" connector > Delete/recreate > Re-enter Client ID/Secret from Atlassian console.
• During consent: Log in as your service account (not personal), it prompts for permissions. -> If "internal server error" here, it's often because the app isn't "installed" yet. So you should complete the full OAuth loop in a browser (hit the authorize URL manually: https://auth.atlassian.com/authorize?audience=api.atlassian.com&client_id=YOUR_ID&scope=your_scopes&response_type=code&redirect_uri=https://chatgpt.com/connector_platform_oauth_redirect).
• After: Test with a simple query like "List my Jira projects" -> if 500, check ChatGPT logs (Settings > Developer > View errors).

3) Enterprise workspace config:

• As admin: ChatGPT > Settings > Workspace > Developer/Connectors > Ensure "Custom MCP connectors" is enabled for your team (beta for full write actions).
• MCP URL: Confirm https://mcp.atlassian.com/v1/sse in connector setup—Enterprise supports it natively. 

4) If Still 500: Which happens more common than you think

• Clear cache/cookies for auth.atlassian.com and chatgpt.com. You can try incognito.
• Regenerate API token on service account (id.atlassian.com > Security > Tokens > Classic scopes including offline_access).
• Test token validity: curl -H "Authorization: Bearer TOKEN" https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/myself (get cloudId from admin.atlassian.com > Site settings > General).

The Enterprise flows are more strict on consent. 

You can refer to this doc:

• ChatGPT Enterprise Connectors (admin enablement).

Best, 

Peter