A
licenseC
qualityC
maintenanceEnhances 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.
22
15 npm
39
MIT
SuperClaude MCP Server
by tinywind
Related Servers
Alternatives to SuperClaude MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to consult Gemini for complex coding problems with session management, file attachments, and conversation persistence.105MIT
- AlicenseBqualityDmaintenanceEnables Claude to offload large codebase analysis to Google Gemini with 1M+ token context windows, persistent sessions, and dramatic token savings.87 npm1MIT
- AlicenseAqualityDmaintenanceIntegrates the local gemini CLI tool with Claude Code, allowing Claude to execute Gemini AI queries via the MCP protocol.17 npm1MIT
- FlicenseBqualityNot gradedmaintenanceEnables Claude Code to use Google Gemini AI capabilities for analyzing PDFs and images, generating and translating text, and reviewing code. Supports both CLI and API backends with different quota limits.478 npm-
- AlicenseAqualityCmaintenanceIntegrates Google's Gemini AI models into Claude Code and other MCP clients to provide second opinions, code comparisons, and token counting. It supports streaming responses and multi-turn conversations directly within your existing AI development workflow.3Apache 2.0
TDQS
C2.8/5.0
Scored across 20 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness5/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues