SuperClaude MCP Server
Related Servers
Alternatives to SuperClaude MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to delegate large-context analysis, code review, test generation, and Google-ecosystem consultation to Gemini models through a local authenticated CLI session, avoiding additional API costs.MIT
- AlicenseCqualityDmaintenanceEnhances Gemini CLI with SuperClaude Framework v4.0.9, providing 22 specialized commands, 14 domain-expert agents, and integration with 6 MCP servers for development, analysis, and automation.2288 npm39MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude clients to consult Gemini through a subscription-authenticated CLI for second opinions, media analysis, and code review; generate images and speech via the google-genai SDK; and prepare or measure media locally. Persistent sessions let follow-up requests continue from prior context while tools return text and file paths rather than binary data.MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to consult Gemini for complex coding problems with session management, file attachments, and conversation persistence.106MIT
- AlicenseBqualityDmaintenanceEnables Claude to offload large codebase analysis to Google Gemini with 1M+ token context windows, persistent sessions, and dramatic token savings.867 npm1MIT
- AlicenseAqualityDmaintenanceIntegrates the local gemini CLI tool with Claude Code, allowing Claude to execute Gemini AI queries via the MCP protocol.11MIT
TDQS
Scored across 20 tools
Most tools have clear, distinct purposes, but there is some overlap between sc_analyze, sc_improve, sc_cleanup, and sc_troubleshoot, which all deal with code modification. However, their descriptions specify different focuses (analysis, enhancement, cleanup, debugging), so an agent can usually select the right one.
All tools consistently use the sc_ prefix with lowercase hyphenated names (e.g., sc_dev-setup, sc_analyze). This uniform pattern makes the tool naming highly predictable and easy to navigate.
With 20 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct development function, from building to deployment. The count feels comprehensive rather than bloated for an all-in-one development assistant.
The tool surface covers the entire development lifecycle—project creation, setup, testing, analysis, debugging, improvement, deployment, migration, security, estimation, documentation, and git operations. There are no obvious gaps that would force an agent into a dead end for common workflows.