[Bug / OAuth]: Goose Desktop v1.45.0: MCP Server that use query parameters fails at connection time in with rmcp "unexpected server response" error
- Vorherrschende Sprache
- Rust
- Sterne
- 54.2k
- Forks
- 6.2k
- Ø Merge
- 3 T. 2 Std.
- Gemergte PRs (30 T.)
- 262
Beschreibung
**Describe the bug**
Cannot connect to the Datadog MCP server via Oauth
**Expected behavior**
When connecting to the Datadog MCP server ( `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core` with a custom query string parameter to configure [toolsets](https://docs.datadoghq.com/mcp_server/setup/?tab=chatgpt#toolsets), the user should be redirected to the OAuth2 login screen (just like in Claude Desktop / ChatGPT) . Instead, we are shown a warning
This started happening after upgrading to Goose Desktop `1.45.0` on MacOS using Apple silicon. Downgrading to `1.44.0` restores connectivity. https://github.com/aaif-goose/goose/releases#release-v1.44.0
---
**Screenshots**
Error message when clicking copy
```
failed to initialize MCP client: Send message error Transport [rmcp::transport::worker::WorkerTransport>] error: unexpected server response: HTTP 401 Unauthorized: {"errors":["Unauthorized"]}, when send initialize request
```
---
**Please provide the following information**
- **OS & Arch:** MacOS, Apple Silicon
- **Interface:** Desktop UI
- **Version:** v1.45.0
- **Extensions enabled:** N/A (Datadog extension is failing to activate)
- **Provider & Model:** Anthropic - Haiku 4.6
---
**Additional context**
The same MCP server connection works in other MCP app hosts (Cursor, Claude Desktop).
From reviewing the 1.45.0 changelog, I didn't see anything that seemed directly related to Auth, but I did notice a major version bump of rmcp: https://github.com/aaif-goose/goose/pull/10584
Do not begin implementation until the issue reaches **Ready** on the [Goose Issues board](https://github.com/orgs/aaif-goose/projects/1).
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.