mcpfoldmcpfold for teams
Standardize your team’s MCP setup from one repo-committed config: everyone folds the same servers to their own clients, a CI drift gate keeps them in sync, and secrets stay references — no hosted gateway required.
Commit one reviewed `mcp.config.jsonc` to your repo. Every teammate runs `mcpfold sync` to fold it into whatever clients they use, so the whole team runs the same, reviewed set of MCP servers without a shared machine or a hosted service. Add `mcpfold diff --check` to CI as a drift gate, and a client config can never silently wander from the committed source.
Secrets stay as references in the committed config — each developer resolves them locally from their own environment or secret manager — so a shared config never carries a raw token. This repo-committed workflow is the whole team wedge, and it is entirely free and local.
When you want shared config, an audit trail, and sync managed for you, the optional hosted cloud adds that on top — and only ever syncs config with secret references, never secret values. It is self-hostable, and mcpfold stays local-first: it is not a hosted enterprise MCP gateway with server-side access control, and does not aim to be.
- Repo-committed config. One reviewed config; everyone folds the same servers to their clients.
- CI drift gate. `mcpfold diff --check` fails the build if a client drifts from the source.
- References, never values. Secrets stay references; the cloud never syncs secret values.
- Optional, self-hostable cloud. Shared config + audit + sync when you want it — or self-host it for free.