Gemini SuperClaude MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_CONFIG_DIR | No | Path to the Claude configuration directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sc:buildC | Universal project builder with intelligent scaffolding (Category: development, Priority: IMPORTANT) |
| sc:implementC | Feature implementation with intelligent persona activation (Category: development, Priority: IMPORTANT) |
| sc:workflowB | Multi-stage workflow orchestration with parallel execution (Category: orchestration, Priority: IMPORTANT) |
| sc:analyzeC | Multi-dimensional codebase analysis with comprehensive insights (Category: analysis, Priority: IMPORTANT) |
| sc:brainstormC | Interactive requirements discovery through Socratic dialogue (Category: orchestration, Priority: IMPORTANT) |
| sc:troubleshootC | Intelligent problem diagnosis and systematic resolution (Category: analysis, Priority: CRITICAL) |
| sc:business-panelC | Multi-expert business analysis with adaptive interaction modes (Category: analysis, Priority: IMPORTANT) |
| sc:improveC | Evidence-based code improvement with systematic refactoring (Category: quality, Priority: IMPORTANT) |
| sc:testC | Comprehensive testing strategy with automation (Category: quality, Priority: IMPORTANT) |
| sc:taskC | Enhanced task management with cross-session persistence (Category: operations, Priority: IMPORTANT) |
| sc:spawnC | Specialized agent spawning and intelligent coordination (Category: operations, Priority: IMPORTANT) |
| sc:explainC | Educational explanations with progressive learning approach (Category: knowledge, Priority: RECOMMENDED) |
| sc:documentC | Comprehensive documentation generation with best practices (Category: knowledge, Priority: RECOMMENDED) |
| sc:cleanupB | Project cleanup and technical debt reduction (Category: maintenance, Priority: RECOMMENDED) |
| sc:gitD | Git workflow assistant with intelligent operations (Category: maintenance, Priority: RECOMMENDED) |
| sc:estimateC | Evidence-based project estimation with risk assessment (Category: planning, Priority: IMPORTANT) |
| sc:designC | System design and architecture orchestration (Category: planning, Priority: IMPORTANT) |
| sc:loadC | Project context loading and cross-session restoration (Category: session, Priority: CRITICAL) |
| sc:saveC | Session state persistence with intelligent context capture (Category: session, Priority: CRITICAL) |
| sc:reflectC | Meta-cognitive reflection and performance analysis (Category: session, Priority: RECOMMENDED) |
| sc:indexC | Command catalog browsing and intelligent discovery (Category: meta, Priority: RECOMMENDED) |
| sc:select-toolC | Intelligent tool selection and optimization guidance (Category: meta, Priority: RECOMMENDED) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
The tools cover a wide range of distinct functionalities (analysis, development, planning, operations, etc.), and their descriptions clearly differentiate between them. However, there is minor overlap between some tools like 'improve' and 'cleanup', and 'reflect' and 'analyze' could be confused, but overall an agent can distinguish them.
All tools use the 'sc:' prefix and lowercase with hyphens for multi-word names, which is consistent. However, the pattern mixes verbs (analyze, build, test) and nouns (cleanup, git, task), lacking a uniform verb_noun structure. This inconsistency can be slightly confusing but still readable.
With 22 tools, the server is quite extensive for a single MCP server. While each tool serves a distinct purpose, the sheer number may be overwhelming and borderline excessive for typical use cases. A more focused set might be better.
The tool set covers a broad range of project lifecycle needs: analysis, planning, implementation, testing, documentation, maintenance, and session management. Minor gaps exist (e.g., no deployment or configuration management), but overall it provides a comprehensive suite for software development assistance.