Skill Detail

Manage agent CLI providers and MCP settings with CC Switch

Use CC Switch to keep provider profiles, MCP servers, prompts, skills, sessions, and usage tracking consistent across Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Published
โญ 76.2k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill manage-agent-cli-providers-and-mcp-settings-with-cc-switch Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
CC Switch desktop app, Claude Code, Codex, Gemini CLI, OpenCode, or OpenClaw, provider credentials, optional MCP server definitions
Install & setup
Install the latest CC Switch release from GitHub or use the upstream macOS Homebrew cask path, then import existing CLI configs and add provider, MCP, prompt, or skill presets from the CC Switch UI.
Author
farion1231
Publisher
Individual
Last updated
May 20, 2026
Quick brief

Use CC Switch when an operator needs a repeatable desktop workflow for managing agent CLI configuration across several runtimes. The workflow is to install CC Switch, import or define provider presets, connect the relevant Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw config locations, then use its MCP, prompt, skill, session, and usage panels to switch providers and keep runtime settings synchronized.

How it works

What this skill actually does

Invoke this instead of hand-editing JSON, TOML, and environment files when a workspace needs controlled provider switching, shared MCP server setup, or repeatable prompt and skill distribution across multiple agent tools. The scope boundary is agent-runtime configuration management; it is not a general LLM gateway, model marketplace, or replacement for the underlying CLI tools.

Inputs are existing agent CLI installations, provider credentials or official-login profiles, MCP server definitions, prompt and skill repositories, and the workspace/config directories to manage. Outputs are updated local runtime configuration files, synchronized MCP and prompt assets, usage dashboards, and a clear rollback path back to official provider profiles.