docs: add Goose MCP integration guide (#831)

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Aru Sharma 2026-06-23 22:45:30 +05:30 committed by GitHub
parent a0cc938f4a
commit ff821e0b4f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 26 additions and 0 deletions

View File

@ -224,6 +224,32 @@ Add to `~/.config/zed/settings.json`:
Zed uses `context_servers` instead of `mcpServers`. Native HTTP support requires Zed v0.214.5 or later.
</Note>
### Goose
[Goose](https://goose-docs.ai/) supports remote MCP servers natively over Streamable HTTP.
The easiest way is to run `goose configure`, choose **Add Extension → Remote Extension (Streamable HTTP)**, and enter the name `honcho`, the URI `https://mcp.honcho.dev`, and the headers `Authorization: Bearer hch-your-key-here` and `X-Honcho-User-Name: YourName`.
Or edit your `config.yaml` directly (on Linux, `~/.config/goose/config.yaml`):
```yaml
extensions:
honcho:
enabled: true
type: streamable_http
name: honcho
description: Honcho persistent memory & personalization
uri: https://mcp.honcho.dev
headers:
Authorization: "Bearer hch-your-key-here"
X-Honcho-User-Name: "YourName"
timeout: 60
```
<Tip>
To teach Goose the recommended memory flow, save the [instructions](https://raw.githubusercontent.com/plastic-labs/honcho/refs/heads/main/mcp/instructions.md) into a `.goosehints` file in your Goose config directory (or a project root). This is Goose's equivalent of Claude Desktop's "Project Instructions". Not sure of your config path? Run `goose info`.
</Tip>
---
## Optional Configuration