MCPs scoped per project, not per machine
Scope MCP servers per project and keep output concise. Developer working across Swift, Go and Kubernetes.
what to steal
Install MCPs at project scope unless you truly need them everywhere.
Our takeaway from the source, not a quote.
cavallin-plugins-scoped-mcp.toml
# Scope MCP servers per project and keep output concise # source: https://www.lucavallin.com/blog/how-i-actually-use-claude-code [rig] who = "Developer working across Swift, Go and Kubernetes" author = "Luca Cavallin" date = "not stated" harness = ["Claude Code"] models = [] [keep] - Plugins: superpowers, Swift/Go LSP, Playwright, Context7, Serena, feature-dev, security check, humanizer - MCP global: Kubernetes (read-only), XcodeBuildMCP - MCP project-scoped: Apple mcpbridge - Output style: Concise [cut] - Unused items
| thing | status | why (per source) |
|---|---|---|
| Unused items | pruned | Post includes a pruning section |
Source: https://www.lucavallin.com/blog/how-i-actually-use-claude-code · checked 2026-10-14
// similar rigs
~/rigs/paulund-herdr-cli.toml2026-10-05
Three desktop apps out, one terminal multiplexer in
steal → Use one session view for all CLIs instead of one app per harness.
CodexClaude CodeOpenCode Codex / Claude Code /
by Paulund
~/rigs/hboon-one-config-three-agent….toml2026-06-27
One config folder, symlinked into three agents
steal → Keep one AGENTS.md and skills folder; symlink it into every harness.
DroidClaude CodeCodex Per-harness config cop
by Hwee-Boon Yar
~/rigs/tartrau-lean-claude-md.tomlundated
CLAUDE.md under 30 lines, detail pushed to path-scoped rules
steal → Keep the always-on file tiny and scope everything else by path.
Claude Code 15 skills
by Thomas Tartrau