MCP server · Engineering and operations

SonarQube Cloud MCP server

SonarQube Cloud in any MCP client, through Memtro: SonarQube Cloud does not publish this server. Memtro's SonarQube Cloud connector reads SonarQube Cloud through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

SonarQube Cloud (SonarCloud) code quality: projects in an organisation, issues (bugs, vulnerabilities, code smells) by project, severity and status, quality gate status, key measures such as coverage and duplication, recent analyses and security hotspots. On request it comments on, tags, assigns and transitions issues (confirm, resolve, accept, false positive, reopen), edits comments, and creates, tags or deletes projects.

Reads

  • sonarcloud_list_projectsProjects in the connected SonarQube Cloud organisation, with key, visibility and last analysis date.
  • sonarcloud_search_issuesIssues found by SonarQube Cloud: bugs, vulnerabilities and code smells, with severity, status, rule, file and line, author and assignee.
  • sonarcloud_quality_gateWhether a project passes its quality gate (OK, WARN, ERROR or NONE) and which conditions fail, with actual values against thresholds.
  • sonarcloud_measuresCurrent measures for a project: bugs, vulnerabilities, code smells, hotspots, coverage, duplication, lines of code and the A–E ratings…
  • sonarcloud_list_analysesRecent analyses of a project, newest first, with the date, the version analysed and the events attached (quality gate changes, version tags).
  • sonarcloud_list_hotspotsSecurity hotspots in a project that need review: the rule's message, file and line, status and resolution.

Acts, when you ask

These change something in SonarQube Cloud. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • sonarcloud_add_issue_commentAdds a comment to a SonarQube Cloud issue, visible to everyone who can see the project.
  • sonarcloud_add_issue_tagsAdds tags to one SonarQube Cloud issue, keeping the tags already on it.
  • sonarcloud_transition_issueMoves one SonarQube Cloud issue through its workflow: confirm, unconfirm, reopen, resolve, close, accept, wontfix, falsepositive, defer…
  • sonarcloud_assign_issueAssigns one SonarQube Cloud issue to the user with the given login, or unassigns it.
  • sonarcloud_set_issue_tagsReplaces the whole tag list on one SonarQube Cloud issue with the tags given; tags not listed are removed, and an empty list removes them all.
  • sonarcloud_edit_issue_commentReplaces the text of a comment on a SonarQube Cloud issue.
  • sonarcloud_create_projectCreates a new, empty project in the connected SonarQube Cloud organisation, with the key and name given, ready for its first analysis.
  • sonarcloud_set_project_tagsReplaces the whole tag list on a SonarQube Cloud project with the tags given; tags not listed are removed.
  • sonarcloud_delete_projectDeletes a SonarQube Cloud project, permanently, with all its analyses, issues and history.

Connect it

First connect SonarQube Cloud on Dashboard → Connections, then add Memtro to your client once. The SonarQube Cloud tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared SonarQube Cloud connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Does the payments service pass its quality gate, and if not, which conditions fail?
  • › What new bugs were found in the payments service this week?
  • › Which security hotspots are still to review on the api project?
  • › Assign that vulnerability to Priya and tag it sprint-12
  • › Mark issue AX-381 as a false positive with a comment explaining why

Questions

Is this an official SonarQube Cloud MCP server?
No. It is Memtro's MCP server with Memtro's SonarQube Cloud connector behind it: the connector reads SonarQube Cloud through its API with the credentials you connect on Dashboard → Connections, and SonarQube Cloud publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in SonarQube Cloud?
Only when you ask, and only what it has been granted: add a comment to a SonarQube Cloud issue; add tags to a SonarQube Cloud issue; move a SonarQube Cloud issue through its workflow (confirm, resolve, accept, false positive, reopen); assign a SonarQube Cloud issue to a user, or unassign it; replace the tags on a SonarQube Cloud issue; edit a comment on a SonarQube Cloud issue; create a SonarQube Cloud project in the organisation; replace the tags on a SonarQube Cloud project; delete a SonarQube Cloud project and its analysis history (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time