What mcpfold does

Four capabilities, one CLI: keep one config for every client, curate tools to cut the context-window tax, keep secrets as references, and preview and guard every change. Go deep on the one that matters to you.

One config, folded out to every client

Write your MCP servers once in a single canonical config, and mcpfold renders each client's own native format — so the same servers show up in all 18 supported clients without hand-editing a different file for each.

Curate tools, cut the context-window tax

Every MCP server dumps its full tool schema into the model's context whether you use those tools or not. Allow- or deny-list tools per server and only what you need loads — the committed benchmark cuts 45 tools to 9 for about 80% fewer tokens.

Secrets as references, never values

Your config carries ${env:…} / ${op:…} references instead of raw tokens, so nothing sensitive is ever written to a client config or committed to git. mcpfold resolves each reference at fold time, from your environment or secret manager.

Sync, diff, and drift control

See exactly what would change before you write it, fold your config out with one command, and catch drift when a client config wanders from the source — in your terminal or as a CI gate.

New here? Install mcpfold or browse the MCP server directory.