gemini-superclaude

Gemini SuperClaude MCP Server exposes the Gemini CLI integration of the SuperClaude framework. It provides 22 /sc: commands for interacting with domain-specific agents (14 specialized agents covering architecture, security, performance, and more) and coordinates with multiple MCP servers to enable complex multi-tool workflows within Gemini CLI. The server's integration allows you to configure a TOML-based or JSON-based Gemini CLI setup so that you can trigger /sc: commands, run business-panel analyses, and maintain cross-session memory with Serena-backed persistence. Typical usage involves installing the MCP server, then wiring Gemini CLI to call the server’s /sc: commands, enabling business-panel workflows and agent collaboration across the included MCP servers (Sequential, Context7, Magic, Playwright, Morphllm, Serena).

Once configured, you can leverage the 22 core /sc: commands for tasks like analysis, brainstorming, implementation planning, testing, documentation, and memory/session management. The 14 agents offer domain-specific perspectives (e.g., system-architect, security-engineer, performance-engineer, python-expert) and can auto-trigger actions based on keywords and contexts. The Business Panel provides nine thought leaders for multi-expert analyses, making it possible to compare approaches and synthesize recommendations across domains. The server also integrates with Gemini CLI via TOML configuration, enabling seamless invocation of /sc: commands from within your existing Gemini workflows.

Prerequisites:

• Node.js v18.x or newer
• Git
• npm (comes with Node.js)

Installation steps:

1. Install the MCP server package globally (recommended):

npm install -g gemini-superclaude-mcp-server

2. Install and configure Gemini CLI integration (generate TOML command configuration):

npm run install-commands

3. Configure Gemini CLI to use the MCP server (example TOML snippet):

{
  "mcpServers": {
    "superclaude": {
      "command": "npx",
      "args": ["-y", "gemini-superclaude-mcp-server"],
      "env": {
        "CLAUDE_CONFIG_DIR": "${HOME}/.claude"
      }
    }
  }
}

4. Verify installation and run basic tests (if you’re developing locally):

npm run validate
npm test

Optional: For local development, clone the repo, install dependencies, and start via Node if you’re not using the global install:

git clone https://github.com/Dianel555/gemini-superclaude-mcp-server.git
cd gemini-superclaude-mcp-server
npm install
# Start the server directly (path may vary if using a local setup)
node ./path/to/superclaude-server.js

Environment and configuration tips:

• CLAUDE_CONFIG_DIR controls where Claude/Gemini stores its configuration and memory; set it to a persistent path like ${HOME}/.claude.
• When using npx installation, ensure you have network access to fetch the package; for offline or offline-build workflows, consider local development mode using the local repository.
• The server integrates with multiple MCP servers (Sequential, Context7, Magic, Playwright, Morphllm, Serena); ensure those services are reachable and compatible with your current SuperClaude framework version (v4.0.9).
• If you encounter permission issues after performing npm install -g, you may need to adjust npm prefix or use sudo on some systems (not generally recommended; prefer nvm/node version managers).
• For Gemini CLI integration, keep the TOML/JSON configuration synchronized with the MCP server changes when updating to v2.0.2 or newer.
• Use npm run validate and npm test to ensure your setup is functioning before deploying to production.