cc-setup
BiswaViraj/cc-setup
Configure plugins e MCP servers do Claude Code em segundos
Ver no GitHubMCP server que simplifica a adição de plugins e servidores MCP do Claude Code a novos projetos. Define suas ferramentas preferidas uma vez em um arquivo de configuração e as reutiliza em qualquer projeto com um único comando, eliminando a necessidade de memorizar IDs de instalação e executar múltiplos comandos CLI.
Instalação
npx convez-ai BiswaViraj/cc-setup1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Reutilizar lista curada de plugins em múltiplos projetos
- Compartilhar configuração de ferramentas com time de desenvolvimento
- Acelerar setup inicial de projetos Claude Code
Veredito

Ferramenta útil para quem trabalha frequentemente com Claude Code e MCP servers. Reduz atrito no setup de novos projetos, mas requer configuração inicial e é dirigida principalmente a desenvolvedores que já usam esse ecossistema.
README
A tradução para o português deste README ainda está na fila.
cc-setup
Claude Code supports plugins (skills, hooks, agents) and MCP servers — but adding them to a new project means remembering install IDs, setting up marketplaces, and running multiple CLI commands every time.
cc-setup lets you define your preferred tools once, then add them to any project with a single command.
- Create
~/.cc-setup.jsonwith your go-to plugins and MCP servers - Run
cc-setupin any project - Pick from your list, choose the scope, done

It ships with a small built-in list of popular plugins, but the real value is your own curated list — set it up once, reuse everywhere.
Add your preferred Claude Code plugins and MCP servers to any project in seconds.
Install
# Run directly
npx @biswaviraj/cc-setup@latest
# Or install globally
pnpm add -g @biswaviraj/cc-setup@latest
cc-setup
Custom tools
Create ~/.cc-setup.json to add your own plugins and MCP servers to the picker:
{
"defaults": ["superpowers", "context-mode", "my-plugin"],
"plugins": [
{
"value": "my-plugin",
"label": "My Plugin",
"hint": "what it does",
"install": "my-plugin@my-marketplace",
"marketplace": "org/repo"
}
],
"mcpServers": [
{
"value": "my-server",
"label": "My Server",
"hint": "what it does",
"command": "npx my-mcp-server"
}
]
}
Your entries are merged with the built-in list. No duplicates.
Plugin fields
| Field | Required | Description |
|---|---|---|
value | yes | Unique ID |
label | yes | Display name |
hint | yes | Short description |
install | yes | Plugin install ID (e.g. my-plugin or my-plugin@marketplace) |
marketplace | no | GitHub org/repo for non-official marketplaces |
MCP Server fields
| Field | Required | Description |
|---|---|---|
value | yes | Unique ID |
label | yes | Display name |
hint | yes | Short description |
command | yes | The command to run (e.g. npx my-mcp-server) |
Quick mode
Set defaults in your config, then:
# Install defaults, just pick scope
cc-setup --quick
# Fully non-interactive
cc-setup --quick --scope local
Scopes
| Scope | Where | Use case |
|---|---|---|
local | .claude/settings.local.json | Just for you, this project |
project | .claude/settings.json | Shared with team (committed to git) |
user | ~/.claude/settings.json | All projects on this machine |
How it works
Under the hood, cc-setup runs:
claude plugins marketplace add <repo>for custom marketplacesclaude plugins install <plugin> -s <scope>for pluginsclaude mcp add <name> -s <scope> -- <command>for MCP servers
That's it. No magic.
License
MIT