Lovie MCP›Goose
Agent
Goose calls MCP servers extensions, spells the URL field uri, and writes YAML rather than JSON. Let goose configure write the file the first time — every field name here differs from the client next to it.
The only value you need
https://mcp.lovie.co/mcp
goose configure
lovie.https://mcp.lovie.co/mcp when it asks for the endpoint URI.300 seconds is a safe default — a formation walkthrough is not a sub-second call.
Goose calls MCP servers extensions. Let goose configure write
the file the first time: every field name here differs from the client next to it, and the
wizard gets them right.
~/.config/goose/config.yaml, if you would rather edit it:
extensions: lovie: enabled: true name: lovie type: streamable_http uri: https://mcp.lovie.co/mcp timeout: 300
Goose spells the URL uri where the rest of the ecosystem says
url, and the transport streamable_http with an underscore
where VS Code says http and JetBrains says streamable-http.
After any hand edit run goose info -v to confirm the file still parses.
$ goose info -v $ goose session > using lovie, list my companies
| Symptom | Cause |
|---|---|
| Extension silently absent | YAML indentation, or url instead of uri. goose info -v reports it. |
| Calls time out | The default timeout is short. Raise timeout to 300. |
enabled: false after configure | The extension was added but not switched on. Flip it, or re-run goose configure and toggle extensions. |