mcs-cli.dev

Managed Claude Stack

A configuration engine for Claude Code. Package your MCP servers, hooks, skills, commands, and settings into shareable tech packs — then sync everywhere.

Get Started View on GitHub
Swift 6.0+macOS 13+MIT License
Terminal — mcs
# Install via Homebrew $ brew install mcs-cli/tap/mcs # Add a tech pack $ mcs pack add mcs-cli/memory [OK] Pack 'Memory' added successfully. # Sync your project $ cd ~/Developer/my-project $ mcs sync [OK] Updated .mcs-project # Verify everything $ mcs doctor
The Problem

Configuration shouldn't
be a full-time job.

You've spent hours getting Claude Code just right. Then reality hits.

Without MCS

  • New machine? Start from scratch.
  • Onboarding? Follow this 47-step wiki.
  • Copy-paste configs, hope nothing drifts.
  • Something broke? Good luck debugging.

With MCS

  • mcs pack add + mcs sync — done.
  • Push a pack, anyone can sync it.
  • Managed settings composition.
  • mcs doctor --fix detects and repairs.
Features

Everything you need,
nothing you don't.

One CLI to manage your entire Claude Code environment.

Tech Packs

Git repos with a YAML manifest. Bundle MCP servers, hooks, skills, commands, agents, and settings.

Convergent Sync

Idempotent operations. Run mcs sync any number of times — it always converges.

Safety First

Backups, dry-run mode, SHA-256 trust verification, and lockfiles for reproducible environments.

Doctor & Fix

Multi-layer diagnostics across all packs. Auto-fix with mcs doctor --fix.

Global & Per-Project

Scope-aware installation. Global packs for your machine, per-project packs for each repo.

Export Wizard

Already have a setup? mcs export generates a tech pack from your existing config.

Tech Packs

A Git repo.
A YAML manifest. That's it.

A tech pack is a Git repository containing a techpack.yaml manifest. It can bundle MCP servers, plugins, hooks, skills, commands, agents, settings, templates, and doctor checks.

Packs are modular — mix and match what you need instead of one monolithic config.

Example Packs

MemoryPersistent memory across sessions DevSettings, git workflows, code nav iOSXcode, simulators, Apple docs
techpack.yaml
identifier: "my-team-pack" Unique identifier displayName: "My Team Pack" description: "Shared configs for my team" components: - id: docs-search MCP server description: "Semantic docs search" mcp: command: "npx" args: ["-y", "docs-mcp-server@latest"] - id: code-review Skill description: "Code review guidelines" skill: path: "skills/code-review.md" templates: CLAUDE.md sections - sectionIdentifier: instructions contentFile: "templates/claude-local.md"
Quick Start

Get started in 4 steps.

From zero to a configured environment in under a minute.

1
Install MCS
brew install mcs-cli/tap/mcs
2
Add a tech pack
mcs pack add mcs-cli/memory
3
Navigate to your project
cd ~/Developer/my-project
4
Sync and verify
mcs sync && mcs doctor
Safety & Trust

Designed to be
non-destructive.

Every operation is idempotent, convergent, and reversible.

Automatic Backups

Timestamped backups before modifying any file with user content.

Dry Run Mode

Preview every change with --dry-run before committing.

SHA-256 Verification

Pack scripts are hashed at install and verified on every load.

Lockfiles

mcs.lock.yaml pins exact commits for reproducible environments.

Convergent Engine

Deselected packs are fully cleaned up. No orphaned artifacts, ever.

Section Markers

User content in CLAUDE.md is preserved — managed sections never touch your edits.

Coming Soon

The Tech Pack Registry.

Discover, search, and share tech packs

A public registry is in the works — browse community packs, find the right setup for your stack, and publish your own. Stay tuned.