Goose MCP Setup: Connect MCP Servers to Goose
What it is
An open-source, on-machine AI agent from Block that automates engineering tasks from the CLI or a desktop app.
How MCP works in Goose
Goose treats MCP servers as "extensions". It supports built-in, stdio, SSE, and Streamable HTTP extensions, configured in YAML or added through the UI.
Config file location
~/.config/goose/config.yaml (on Windows %APPDATA%\Block\goose\config\config.yaml) lists MCP servers under an extensions map with type: stdio.
Add your first server
A good first server is Playwright MCP — Microsoft's browser automation server. It runs locally over stdio via npx, needs no API key, and gives the agent a real browser to drive. Here is the verified Goose config:
extensions:
playwright:
name: playwright
type: stdio
cmd: npx
args:
- "@playwright/mcp@latest"
enabled: true
timeout: 300Restart or reload Goose after saving, then confirm the server's tools show up. Swap in any other server from the directory using the same structure.
Transports & platforms
| Transports | stdio, SSE, Streamable HTTP |
|---|---|
| Platforms | macOS, Linux, Windows |
| License | Open source |
| Vendor | Block |
FAQ
Does Goose support MCP?
Yes. Goose works as an MCP client over stdio, SSE, Streamable HTTP. Goose treats MCP servers as "extensions". It supports built-in, stdio, SSE, and Streamable HTTP extensions, configured in YAML or added through the UI.
Where is the Goose MCP config?
~/.config/goose/config.yaml (on Windows %APPDATA%\Block\goose\config\config.yaml) lists MCP servers under an extensions map with type: stdio. The verified example above shows the exact structure it expects.
Which MCP servers work with Goose?
Any server that speaks a transport Goose supports (stdio, SSE, Streamable HTTP). Browse the MCP server directory on this site to find databases, browser automation, API integrations, and dev tools, then add them using the config format above.