The codeguilds CLI knows exactly where to put every package and how to wire it into your AI editor — automatically.
npx codeguilds install <package-slug>You could copy-paste config from the web UI. Or you could let the CLI do it in one command.
Every package carries its own install blueprint. The CLI reads it and writes the exact JSON into the right settings file — no copy-pasting.
MCP servers and hooks are merged into your existing settings.json. Your other config is never touched.
`codeguilds uninstall` reverses every change — removes the MCP entry, deletes the hook, cleans the file. One command to undo.
Installed packages are tracked in `.codeguilds-lock.json`. Commit it to share your exact setup with your team.
Use `--project` to install into a project-local `.claude/` folder instead of your global config. Great for team repos.
Find the right package without leaving your editor. `codeguilds search [query]` returns results ranked by downloads.
npx codeguilds install <slug>Or install globally for a shorter command:
npm install -g codeguildscodeguilds search filesystem
codeguilds info <package-slug>codeguilds install <package-slug>The CLI merges the MCP server entry into ~/.claude/settings.json automatically.
For MCP servers and hooks, restart your editor to pick up the new config. Skills, agents, and prompts are available immediately.
The CLI reads the install_config stored in the registry and places each file exactly where your AI editor expects it.
MCP Servers
→ ~/.claude/settings.json → mcpServers
Restart your editor to activate
Hooks
→ ~/.claude/settings.json → hooks
Active immediately on next run
Skills & Prompts
→ ~/.claude/commands/[filename].md
Available as /commands in Claude Code
Agents
→ ~/.claude/agents/[filename].md
Available as sub-agents
| codeguilds install <slug> | Install a package globally |
| codeguilds install <slug> --project | Install into project .claude/ |
| codeguilds uninstall <slug> | Remove and undo all config changes |
| codeguilds search <query> | Search the registry |
| codeguilds info <slug> | Show package details |
| codeguilds list | List installed packages |
Add --project to any install/uninstall command to scope changes to the current project:
codeguilds install mcp-postgres --project
# → writes to ./.claude/settings.json instead of ~/.claude/settings.json| codeguilds login | Log in via GitHub OAuth |
| codeguilds logout | Log out and clear saved session |
| codeguilds whoami | Show currently logged-in user |
| codeguilds profile | View your publisher profile and tier |
| codeguilds publish | Publish a new package (interactive wizard) |
| codeguilds update <slug> | Publish a new version of an existing package |
| codeguilds rate <slug> --stars <1-5> | Rate a package 1–5 stars |
| codeguilds follow <slug> | Follow a package for updates |
| codeguilds unfollow <slug> | Unfollow a package |
Requires a free account. Run codeguilds login once — opens a browser for GitHub OAuth and saves a token to ~/.codeguilds/auth.json.
Does the CLI need authentication?
Basic commands (install, search, info) are fully public — no login needed. Run codeguilds login to authenticate via GitHub OAuth and unlock publishing, rating, and following. Your session token is saved locally in ~/.codeguilds/auth.json.
Where does the lock file go?
`.codeguilds-lock.json` is created in the directory where you run the install command — usually your project root or home directory.
What if a package doesn't have install_config?
The CLI will tell you so and point you to the source URL. You can still install it manually. We encourage publishers to add install configs.
Can I use it in CI or scripts?
Yes. All commands exit with code 0 on success and 1 on failure, so they compose naturally into shell scripts and CI pipelines.
Will it touch my existing settings?
Only additively. The CLI reads your existing .claude/settings.json and merges new entries in. It never deletes unrelated config.
Browse the registry and find your first package — or publish your own.