MCP-324 Remove namespace from proxied servers

[nquinquenel]

No description provided.

[hashicorp-vault-sonar-prod]

MCP-324

[sonarqubecloud]

SonarQube reviewer guide

Summary: Remove the namespace field from proxied MCP server configuration and expose tools with their original names instead of prefixed names.

Review Focus:

• The namespace field has been completely removed from the configuration model (ProxiedMcpServerConfig), parser, and all JSON configs. Ensure this breaking change is intentional and documented.
• Tool naming has changed from namespaced format (e.g., context/analyze_code) to original names (e.g., analyze_code). This could cause collisions when multiple servers expose tools with identical names—verify this is acceptable or if there's a conflict resolution strategy.
• The ToolMapping record signature changed, removing the namespace parameter. Check all callers are updated.
• Test assertions were updated to match the new naming convention; verify the test expectations align with the desired behavior, especially in ProxiedToolsLoaderMediumTest where multiple servers now return only 2 tools instead of 4.

Start review at: src/main/java/org/sonarsource/sonarqube/mcp/client/ProxiedMcpServerConfig.java. This is the core data model change—removing the namespace field from the record definition and validation logic is the foundation for all downstream changes. Understanding the removal rationale here will clarify

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 Dependency risks

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud