Skip to content

Application Development

SonarQube Server MCP connector

The SonarQube Server connector lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.

Connect on Elaichi How to connect
  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List all SonarQube Server projects with public visibility.

Working in SonarQube Server with Elaichi

  • List all SonarQube Server projects
  • List all SonarQube Server version
  • List all SonarQube Server me
Ask anything…
Governance / Audit log Last 24 hours
SonarQube Server List all SonarQube Server me Emily Carter · Claude · 9:41 AM Done
SonarQube Server List all SonarQube Server version Emily Carter · Claude · 9:41 AM Done
SonarQube Server List all SonarQube Server projects Emily Carter · Claude · 9:41 AM Done
SonarQube Server Create a SonarQube Server project Megan Brooks · ChatGPT · 9:38 AM Done
SonarQube Server SonarQube Server projects update key Ryan Hayes · Cursor · 9:35 AM Done

How to connect SonarQube Server to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

SonarQube Server MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

SonarQube Server MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

SonarQube Server MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

SonarQube Server MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

SonarQube Server MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect SonarQube Server to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Connect SonarQube Server on Elaichi See pricing

What teams do with SonarQube Server through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in SonarQube Server is logged.

  • 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.”

See all 249 SonarQube Server tools →

What connecting SonarQube Server gets you

6 screens from Elaichi, each doing one job for your SonarQube Server account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about projects, read the answer.

Plain questions return live SonarQube Server projects, users and notifications.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.

Every client reaches SonarQube Server over OAuth, no SDK, no shared API key.

ElaichiTools
Tool Action Description
List all SonarQube Server projects List Search for projects or views to administrate them in SonarQube Server. Returns key, name, qualifier, visibility, lastAnalysisDate (all branches), revision (main branch), and managed status for each project.
SonarQube Server projects bulk delete Delete Delete one or several projects in SonarQube Server. Requires at least one of the following parameters: analyzedBefore, projects, or q. Only the first 1000 filtered projects are considered. No response body is returned.
Create a SonarQube Server project Create Create a project in SonarQube Server. Requires 'name' and 'project' parameters. Returns the newly created project's key and name. If project is on a DevOps Platform, use the import endpoint instead.
Delete a SonarQube Server project by ID Delete Delete a project in SonarQube Server. Requires id. Returns success status indicating project deletion.
SonarQube Server projects update key Update Update project and all its sub-components keys in SonarQube Server. Requires from and to parameters. The response returns the status of the key update operation.

Tool catalog

249 SonarQube Server tools are ready now.

Projects, users, groups, notifications and ALM integrations, with no custom code written.

ElaichiToolboxes
Name Source template Tools Created

Platform Engineering toolbox

SonarQube Server · projects and visibility

 SonarQube Server starter 18 Mar 4, 2026

QA toolbox

SonarQube Server · project quality reviews

 — 9 Mar 2, 2026

Security toolbox

SonarQube Server · project access and users

 — 24 Feb 27, 2026

DevOps toolbox

SonarQube Server · ALM integrations

 SonarQube Server starter 6 Feb 19, 2026

Engineering Managers toolbox

SonarQube Server · user groups and members

 — 31 Jan 30, 2026

Release toolbox

SonarQube Server · notifications and versions

 — 12 Jan 22, 2026

Toolboxes

Each team gets its own toolbox.

Curate SonarQube Server toolboxes per team so platform and QA see different tools.

ElaichiConnections
Connection Scope Status Access
SO

SonarQube Server (Platform)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
SO

SonarQube Server (QA Europe)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
SO

SonarQube Server (Security)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
SO

SonarQube Server (Mobile Apps)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
SO

SonarQube Server (Data Services)

Connected by Ryan Hayes

 Personal • Active Not shared
SO

SonarQube Server (Release Engineering)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Shared connections

Teammates use connections, never credentials.

See who connected each SonarQube Server account and which teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

[email protected]

 SonarQube Server Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

[email protected]

 SonarQube Server Projects Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

[email protected]

 SonarQube Server Projects List Toolbox

Audit log

Every project change has a name on it.

When, who, what happened, type and resource, appended for each SonarQube Server call.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

SonarQube Server digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch projects

    SonarQube Server

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve

  6. Post the digest

    SonarQube Server

    Queued

Automations

A schedule ships the quality digest.

Fetch SonarQube Server projects, group them, draft a digest, approve, post it back.

SonarQube Server health

Refreshed 4 minutes ago · every 15 minutes · from the projects collection

Live

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%

Collections and dashboards

Project health arrives without being asked.

Four metrics, 14 days of projects created and a team breakdown, computed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for SonarQube Server

All three can connect SonarQube Server to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for SonarQube Server, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over SonarQube Server tools Allow or restrict single SonarQube Server tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per SonarQube Server call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

More from the catalog

Browse all 650+ connectors →

Questions, answered

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, Microsoft Copilot, 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 role, for example to read-only, but it can never grant access that SonarQube Server itself has not granted.

Can my team share one SonarQube Server connection?

Yes. One person connects SonarQube Server in Elaichi and shares the connection with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every project change or user lookup.

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 restricting project deletion, bulk deletion, key changes or visibility changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot and every other client together.

Does the SonarQube Server MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. SonarQube Server is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for SonarQube Server?

Yes. Both let Claude, ChatGPT or Cursor use SonarQube Server. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every SonarQube Server call.

How is Elaichi different from Composio for SonarQube Server?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to SonarQube Server: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put SonarQube Server in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

Connect SonarQube Server Talk to us

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot