Share with a team

Pegboard doesn’t push anything to other machines. Each person pulls the config and applies it.

Commit the stack

Commit pegboard.yaml and pegboard.lock. Everyone then runs:

pegboard apply

It works like package.json and npm install. Pegboard keeps project state in .pegboard/state.json, which should stay out of git.

Check for changes in CI

Both commands exit with 2 when there’s something to report:

pegboard plan --exit-code
pegboard drift --exit-code

Exit code	Meaning
0	No changes
2	There are changes or drift
1	Error

Add --json to get stable output for scripts.

Limit which MCPs are allowed

A stack can declare the MCPs it allows:

policy:
  allow_mcps: [github, linear]

plan and apply fail if the stack includes anything else:

error: /path/to/pegboard.yaml: policy.allow_mcps does not allow: notion

Roll out to a fleet

To enforce a setup on every laptop, have your existing tooling run pegboard apply. Ansible, an MDM, or each agent’s managed settings can all do this.