Add MCP servers to Goose

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

Set up Goose 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 Goose. Write your servers into Goose's own config (/Users/you/.config/goose/config.yaml) under its `extensions` key.mcpfold sync

What mcpfold writes for Goose

Config file

/Users/you/.config/goose/config.yaml

Windows: C:\Users\you\AppData\Roaming\Block\goose\config\config.yaml

Config key

extensions

Secrets

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

Remote servers

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

After sync

Changes are picked up without restarting Goose.

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 Goose. Names are used only to describe compatibility.