Sonarqube MCP Server vs Next Devtools MCP
A side-by-side look at the Sonarqube MCP Server and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sonarqube MCP Server for developer tools work over a hosted endpoint; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Sonarqube MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SONARQUBE_TOKEN, SONARQUBE_ORG, SONARQUBE_URL, SONARQUBE_PROJECT_KEY. - You want tools like
analyze_code_snippet, projectKey, filePath.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 61/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SONARQUBE_TOKENSONARQUBE_ORGSONARQUBE_URLSONARQUBE_PROJECT_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 665 | 829 |
| Directory activity | 2 views 0 installs 0 upvotes | 8 views 0 installs 1 upvotes |
| Tools | 80 | 4 |
| Full listing | View Sonarqube MCP Server | View Next Devtools MCP |
Tools & capabilities
Sonarqube MCP Server tools 80
analyze_code_snippetAnalyze file content with SonarQube analyzers to identify code quality and security issues. Always analyzes the complete file content for accuracy. Optionally filter results to a specific code snippet.projectKeyThe SonarQube project key - _Required String_ _(Ignored when `SONARQUBE_PROJECT_KEY` is defined)_filePathProject-relative path of the file to analyze (e.g., `src/main/java/MyClass.java`). Used when the workspace is mounted at `/app/mcp-workspace` - _String_fileContentComplete file content as a string. Required when workspace is not mounted - _String_codeSnippetCode snippet to filter issues (must match content in fileContent) - _String_languageLanguage of the code (e.g., 'java', 'python', 'js', 'ts', 'tsx', 'jsx') - _String_scopeScope of the file: MAIN or TEST (default: MAIN) - _String_analyze_file_listAnalyze files in the current working directory using SonarQube for IDE. This tool connects to a running SonarQube for IDE instance to perform code quality analysis on a list of files.file_absolute_pathsList of absolute file paths to analyze - _Required String[]_toggle_automatic_analysisEnable or disable SonarQube for IDE automatic analysis. When enabled, SonarQube for IDE will automatically analyze files as they are modified in the working directory. When disabled, automatic analysis is turned off.enabledEnable or disable the automatic analysis - _Required Boolean_run_advanced_code_analysisRun Vortex analysis on a single file. On Cloud, use the optional `organization` argument when no organization is fixed by `SONARQUBE_ORG`; use `list_organizations` if ambiguous. SonarQube Server uses the nil UUID placeholder.- +68 more on the listing page
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Sonarqube MCP Server
{
"mcpServers": {
"sonarqube-mcp-server": {
"url": "https://your-server:8443/mcp"
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Sonarqube MCP Server is categorized under Developer Tools and uses a remote HTTP/SSE transport. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Sonarqube MCP Server for developer tools work and Next Devtools MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Sonarqube MCP Server has no declared pricing — check the project's own site. Auth: api key required. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sonarqube-mcp-server and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sonarqube MCP Server has a quality signal of 61/100 (Good) with 2 views, 0 installs and 665 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 829 GitHub stars.