Application Development
SonarQube Cloud MCP connector
The SonarQube Cloud connector lets Claude, ChatGPT, Cursor and other AI clients look up the users, groups, notification settings and account details in your SonarQube Cloud organization, with every request running as the person who signed in and recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
4 tools
How to connect
How to connect SonarQube Cloud to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SonarQube Cloud once
-
Open Connections, choose Add connection, and pick SonarQube Cloud.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SonarQube Cloud API key. One person generates a token in SonarQube Cloud and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect SonarQube Cloud to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect SonarQube Cloud to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect SonarQube Cloud to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect SonarQube Cloud to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with SonarQube Cloud through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering management
See who has a SonarQube Cloud seat
Ask for the full list of people in your SonarQube Cloud organization before a renewal or a headcount review, and get names and accounts back in one answer instead of paging through the members screen.
-
IT
Check group membership during offboarding
When someone leaves, ask which SonarQube Cloud groups still include them and which groups exist at all, so nothing is missed when their access is removed.
-
Security
Review groups before an access audit
Pull the list of SonarQube Cloud groups and the users behind them into a document your auditor can read, without anyone exporting spreadsheets by hand.
-
DevOps
Find out which alerts you are subscribed to
Ask what notifications your SonarQube Cloud account currently sends you, so you know why an alert about a failed quality gate or a new issue did or did not arrive.
-
Engineering
Confirm your own account details
Check the login, name and email SonarQube Cloud has on file for you when a colleague cannot find you in a group or a mention is going to the wrong person.
-
Compliance
Answer who can see code quality results
Produce a plain-language summary of the users and groups in SonarQube Cloud for a quarterly access review, drawn from the live organization rather than a stale export.
Try asking
- “List every SonarQube Cloud group and its member count.”
- “Which users have notifications turned on this week?”
- “Show SonarQube Cloud users added since last Monday.”
AI tools
SonarQube Cloud tools for your AI agents
4 tools are ready to call through Elaichi's MCP endpoint the moment you connect SonarQube Cloud, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting SonarQube Cloud gets you
6 screens from the product, each doing one job for your SonarQube Cloud account.
The agent
Ask about SonarQube Cloud users in plain language.
Type a question and get answers read from live users, groups and notifications.
- users
- groups
- notifications
- memberships
Ask Elaichi to work across your apps.
List every SonarQube Cloud group and its member count.
Which users have notifications turned on this week?
Show SonarQube Cloud users added since last Monday.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Reach SonarQube Cloud from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
All 4 SonarQube Cloud tools are ready now.
Browse tool names, resources and methods for users, groups and notifications, no custom code.
- List all SonarQube Cloud users
- List all SonarQube Cloud groups
- List all SonarQube Cloud notifications
- List all SonarQube Cloud me
ElaichiToolsToolboxes
Every team gets its own SonarQube Cloud toolbox.
Curate one toolbox per team so each group sees only relevant tools.
- Engineering
- Platform
- QA
- Security
ElaichiToolboxesShared connections
Teammates query SonarQube Cloud without a credential.
See who connected each account and how many teams and members use it.
- Core Platform
- Mobile Apps
- QA Automation
- Security Review
ElaichiConnectionsAudit log
Answer who read which SonarQube Cloud groups.
Every call records when, who, what happened, type and resource in append-only order.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and the digest ships.
Six steps fetch users, group them, draft a digest, get approval, post back.
SonarQube Cloud digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch users
SonarQube Cloud
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
SonarQube Cloud
Queued
Collections and dashboards
SonarQube Cloud health, counted not guessed.
Four metrics, fourteen days of records created and a team breakdown, refreshed on schedule.
SonarQube Cloud health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Core Platform 34%
Mobile Apps 27%
QA Automation 21%
Security Review 18%
FAQ
Frequently asked questions
How do I connect SonarQube Cloud to Claude?
Two steps. First, connect SonarQube Cloud in Elaichi by pasting an API key from your SonarQube Cloud account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can look up SonarQube Cloud users, groups and notifications for you.
Does SonarQube Cloud work with ChatGPT and Cursor as well as Claude?
Yes. Once SonarQube Cloud is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect SonarQube Cloud once and every client you use picks it up.
What can an AI agent actually do with my SonarQube Cloud data?
With this connector an agent can list the users in your SonarQube Cloud organization, list the groups and who belongs to them, show the notifications your account is subscribed to, and show your own account details. That covers questions like who has a seat, which groups a departing colleague is in, and why a quality gate alert did or did not reach you. It reads this information; it does not change anything in SonarQube Cloud.
Does connecting SonarQube Cloud give the AI access to my whole organization?
No. Every request runs with the SonarQube Cloud permissions of the person who signed in, so an agent sees exactly the users, groups and notifications that person can already see, and nothing more. Elaichi can narrow that further with restrictions, but it can never widen access beyond what SonarQube Cloud itself allows that person.
Can I stop an agent from deleting or changing things in SonarQube Cloud?
This SonarQube Cloud connector only reads: it lists users, groups, notifications and your own account, and it has no way to create, edit or delete anything. Even so, Elaichi lets you restrict each action individually, and any action you block is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a SonarQube Cloud connection when someone leaves?
Offboarding a person in Elaichi ends their access to SonarQube Cloud through every AI client at once. If they had shared a SonarQube Cloud connection with a team, that connection keeps working for everyone else. If you want it gone entirely, disconnecting SonarQube Cloud once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client in one step.
Put SonarQube Cloud in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.