Connect a client
Register the Goono MCP server in Claude Code, Claude Desktop, Cursor, and VS Code
The Goono MCP server exposes a single Streamable HTTP endpoint (POST /mcp) authenticated with the X-Goono-Key header. Any client that supports HTTP transport with custom headers only needs the URL and the header.
| Item | Value |
|---|---|
| Server URL | https://prd-mcp.goono.xyz/mcp |
| Auth header | X-Goono-Key: gno_live_<key_id>_<secret> |
| Transport | Streamable HTTP (stateless). No SSE, no stdio |
Replace gno_live_<key_id>_<secret> in the examples with your key. Staging keys start with gno_test_.
Register from the terminal:
claude mcp add --transport http goono https://prd-mcp.goono.xyz/mcp \
--header "X-Goono-Key: gno_live_<key_id>_<secret>"- Run
/mcpin Claude Code and confirmgoonoshows connected. - Ask "show me my projects" — the client calls
get_methenlist_projects.
Add --scope project to store it in .mcp.json for a single project. The key then lives in that file, so do not commit it.
Other clients
Windsurf, Codex, and any client that supports "HTTP transport + custom headers" can be configured with the same URL and header. Clients without header support can use the mcp-remote wrapper shown for Claude Desktop.
The claude.ai web connector is not supported
Custom connectors on claude.ai support OAuth only and cannot send custom headers. The Goono MCP server authenticates with an API key header, so it cannot be added there today.
Verify the connection
The server is connected when this sequence works:
get_me— returns the key owner, workspace, and scopes.list_projects— returns the projects the key owner belongs to.
Repeated 401s usually mean a wrong header name (X-Goono-Key) or key prefix (gno_live_ / gno_test_). The server checks only that the header exists and has a valid prefix; validity is decided by the Goono backend.