mcpfoldAn open-source, local-first alternative to an MCP gateway
MCP gateways centralize your MCP servers behind a service — useful for teams, but it means running (or paying for) a server. mcpfold is an open-source, local-first alternative: it manages your MCP config on your own machine and folds it out to every client, with per-server tool curation and secret references, and no gateway to operate. If you want the benefits of one source of truth without standing up infrastructure, mcpfold is the lighter-weight option.
| Hosted SaaS gateway | Self-hosted gateway | mcpfold | |
|---|---|---|---|
| Runs where | A vendor’s servers | A server you operate | Locally, as a CLI — no server |
| Infrastructure to run | None (theirs) | Yes — you host it | None — it’s in the launch path |
| One source for many clients | Varies by tool | Varies by tool | Yes — folds to each client’s native format |
| Open source | Varies | Yes | Yes — MIT, free CLI |
| Secret handling | Stored by the service | Stored by your instance | References resolved locally; values never synced |
| Per-server tool curation | Varies by tool | Varies by tool | Allow / deny lists, deterministic |
| Team RBAC / org audit | Yes — their focus | Yes | Not a goal — local-first (optional cloud for sharing) |
| Best for | Teams wanting a managed gateway | Teams that must self-host a gateway | Anyone wanting one config across their own clients, no server |
A gateway is the right shape when an organization wants to run MCP servers centrally, behind access control and an audit trail — that is a real, different job, and tools built for it fit teams that need it. The trade-off is operational: a SaaS gateway is another vendor in your stack, and a self-hosted one is another service to run and secure.
mcpfold takes the opposite, local-first approach. It keeps one canonical config on your machine and folds it out to every client in that client’s native format, curates which tools each client loads to cut context tokens, and stores secrets as references that are resolved at launch — never written to disk. There is nothing to host: the curation happens in a shim already in the launch path.
mcpfold is deliberately not a hosted, multi-tenant gateway: there is no server-side RBAC or org audit, and it does not run servers for you. If you opt into the optional cloud to share config across a team, only the config with secret references is synced — never secret values. For an individual or a small team that wants one honest source of truth without standing up infrastructure, that is exactly the point.
Related
- Where mcpfold fits vs a gateway
- How to reduce MCP token usage
- How mcpfold handles secrets
- Install mcpfold
mcpfold is an independent, open-source project and is not affiliated with or endorsed by the MCP project or any other tool named here. Comparisons describe categories factually.