Goose

Goose calls MCP servers extensions and adds them through an interactive prompt rather than a file you edit. goose configure, then Add Extension, then Remote Extension (Streaming HTTP).

Without a key

goose configure

◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◇  What would you like to call this extension?
│  wellworn
│
◇  What is the Streaming HTTP endpoint URI?
│  https://mcp.wellworn.dev/mcp
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◇  Would you like to add a description?
│  No
│
◇  Would you like to add custom headers?
│  No
│
└  Added wellworn extension

With a key

Answer Yes at the custom headers prompt and give the header in two parts.

◆  Would you like to add custom headers?
│  Yes
│
◇  Header name:
│  Authorization
│
◇  Header value:
│  Bearer ww_your_key
│
◇  Add another header?
│  No

In Goose Desktop the same fields are under Extensions, Add custom extension, with Type set to Streamable HTTP and the key entered under Request Headers.

Confirm it works

The prompt ends with Added wellworn extension. From then on the eight tools are offered to the model in every session: recommend, compare, alternatives, traps, skill, design, docs, submit_trap.

To try it without saving anything, start one session with the extension attached:

goose session --with-streamable-http-extension "https://mcp.wellworn.dev/mcp"

What breaks

The menu has a Remote Extension (SSE) entry directly above the Streaming HTTP one. Picking it points Goose at a transport this server does not speak.

The timeout prompt is in seconds and defaults to 300.

Verified 2026-09-08 against block.github.io