Add MCP servers to Gemini CLI

Manage Gemini CLI’s MCP servers from one canonical config with mcpfold — the free, open-source CLI. Write your servers once and fold them out to Gemini CLI’s own mcpServers config, with secrets kept as references, not hardcoded values.

Set up Gemini CLI in 4 steps

Install mcpfold. Install the free, open-source mcpfold CLI — no account required.npm install -g mcpfold
Create your config. Create one canonical mcp.config.jsonc — the single source of truth mcpfold folds out to every client.mcpfold init
Add a server. Add an MCP server from the registry (secrets stay references, versions stay pinned), or run `mcpfold import` to pull in servers you already configured.mcpfold add <server> --from-registry
Fold it out to Gemini CLI. Write your servers into Gemini CLI's own config (/Users/you/.gemini/settings.json) under its `mcpServers` key.mcpfold sync

What mcpfold writes for Gemini CLI

Config file

/Users/you/.gemini/settings.json

Windows: C:\Users\you\.gemini\settings.json

Config key

mcpServers

Secrets

Secrets stay as `${env:…}` / `${op:…}` references; mcpfold's launcher resolves them at run time, so Gemini CLI's config file never contains a raw token.

Remote servers

Gemini CLI reaches http/sse remotes natively — mcpfold writes a native remote entry, no bridge needed.

After sync

Changes are picked up without restarting Gemini CLI.

Looking for servers to add? Browse the MCP server directory — every entry adds in one mcpfold add. Or see the install options.

mcpfold is an independent, open-source project and is not affiliated with or endorsed by Gemini CLI. Names are used only to describe compatibility.