Application Development
SonarQube Server MCP connector
The SonarQube Server connector lets Claude, ChatGPT, Cursor and other MCP clients list, create and tidy SonarQube Server projects, review users and groups, manage notifications and link repositories, with each request running as the signed-in person 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.
249 tools
How to connect
How to connect SonarQube Server to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect SonarQube Server once
-
Open Connections, choose Add connection, and pick SonarQube Server.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a SonarQube Server API key. One person generates a token in SonarQube Server 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 Server 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 Server 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 Server 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 Server 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 Server through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Take stock of every project
Ask for a list of every SonarQube Server project, then spot the ones that are duplicated, misnamed or no longer tied to code anyone ships.
-
Platform
Set up a new project in seconds
Create the SonarQube Server project for a new service, give it the right key and set it to public or private without leaving the chat.
-
Security
Review who has access and how
Pull the list of SonarQube Server users and user groups to confirm that contractors are gone, groups match team structure and nobody holds access they should not.
-
DevOps
Link repositories to the right projects
See the repositories available in Bitbucket, GitLab or Azure DevOps and bind each one to its SonarQube Server project so analysis follows the code.
-
Engineering management
Clean up after a reorg
Rename project keys to the new convention, change visibility for projects that moved teams, and retire projects for services that were shut down.
-
Engineering
Get alerts to the right people
Check which SonarQube Server notifications are set up, add the ones a team is missing and remove the ones that only add noise.
Try asking
- “List all SonarQube Server projects with public visibility.”
- “Which users sit in the platform-engineering user group?”
- “Show notifications configured on the payments-api project.”
AI tools
SonarQube Server tools for your AI agents
249 tools are ready to call through Elaichi's MCP endpoint the moment you connect SonarQube Server, 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 Server gets you
6 screens from the product, each doing one job for your SonarQube Server account.
The agent
Ask about projects, read the answer.
Plain questions return live SonarQube Server projects, users and notifications.
- projects
- users
- user groups
- notifications
Ask Elaichi to work across your apps.
List all SonarQube Server projects with public visibility.
Which users sit in the platform-engineering user group?
Show notifications configured on the payments-api project.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Every client reaches SonarQube Server over OAuth, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
249 SonarQube Server tools are ready now.
Projects, users, groups, notifications and ALM integrations, with no custom code written.
- List all SonarQube Server projects
- SonarQube Server projects bulk delete
- Create a SonarQube Server project
- Delete a SonarQube Server project by ID
ElaichiToolsToolboxes
Each team gets its own toolbox.
Curate SonarQube Server toolboxes per team so platform and QA see different tools.
- Platform Engineering
- QA
- Security
- DevOps
ElaichiToolboxesShared connections
Teammates use connections, never credentials.
See who connected each SonarQube Server account and which teams and members share it.
- Platform
- QA Europe
- Security
- Mobile Apps
ElaichiConnectionsAudit log
Every project change has a name on it.
When, who, what happened, type and resource, appended for each SonarQube Server call.
- 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 ships the quality digest.
Fetch SonarQube Server projects, group them, draft a digest, approve, post it back.
SonarQube Server digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch projects
SonarQube Server
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 Server
Queued
Collections and dashboards
Project health arrives without being asked.
Four metrics, 14 days of projects created and a team breakdown, computed on schedule.
SonarQube Server health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Platform 34%
QA Europe 27%
Security 21%
Mobile Apps 18%
FAQ
Frequently asked questions
How do I connect SonarQube Server to Claude?
First connect SonarQube Server in Elaichi, which asks you to paste a SonarQube Server API key that you generate from your own account, so there is no OAuth application to register and no client ID or secret to create. Then open Claude, go to Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once, and from then on it can work with your SonarQube Server projects as you.
Does SonarQube Server work with ChatGPT and Cursor as well as Claude?
Yes. SonarQube Server is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing separate to set up per client.
What can an AI agent actually do with my SonarQube Server data?
Through Elaichi, an agent can list every SonarQube Server project, create new ones, rename project keys, change a project's visibility and retire projects you no longer need. It can also show you SonarQube Server users and user groups, manage notifications, and list repositories in Bitbucket, GitLab or Azure DevOps so they can be linked to projects. Short, concrete asks such as "list our private projects" or "who is in the security group" work better than long paragraphs, because the agent searches a large set of SonarQube Server actions to find the right one.
Does connecting SonarQube Server give the AI access to every project?
No. Every request runs under the SonarQube Server API key of the person who signed in, so the agent sees only the projects, users and settings that person can already see in SonarQube Server. Elaichi can narrow that further for a team, for example to read-only, but it can never grant access that SonarQube Server itself has not granted.
Can I stop an agent from deleting or changing things in SonarQube Server?
Yes. Restrictions in Elaichi apply per action, so you can allow listing SonarQube Server projects and users while blocking project deletion, bulk deletion, key changes or visibility changes. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, accidental or otherwise, can reach it.
What happens to a SonarQube Server connection when someone leaves?
When a person is offboarded in Elaichi, their access to SonarQube Server through every AI client ends at once. A SonarQube Server connection that was shared with a team keeps working for everyone else on that team. If you want to remove SonarQube Server entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Put SonarQube Server in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.