Skip to content

Commit f85198a

Browse files
Version Packages
1 parent 7bb79eb commit f85198a

19 files changed

+96
-69
lines changed

.changeset/brave-lions-glow.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

.changeset/busy-weeks-hang.md

Lines changed: 0 additions & 6 deletions
This file was deleted.

.changeset/cyan-cycles-pump.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

.changeset/funky-baths-attack.md

Lines changed: 0 additions & 8 deletions
This file was deleted.

.changeset/heavy-walls-swim.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

.changeset/oauth-error-http200.md

Lines changed: 0 additions & 7 deletions
This file was deleted.

.changeset/respect-capability-negotiation.md

Lines changed: 0 additions & 14 deletions
This file was deleted.

.changeset/shy-times-learn.md

Lines changed: 0 additions & 8 deletions
This file was deleted.

.changeset/tender-snails-fold.md

Lines changed: 0 additions & 6 deletions
This file was deleted.

packages/client/CHANGELOG.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# @modelcontextprotocol/client
2+
3+
## 2.0.0
4+
5+
### Patch Changes
6+
7+
- [#1343](https://github.com/modelcontextprotocol/typescript-sdk/pull/1343) [`4b5fdcb`](https://github.com/modelcontextprotocol/typescript-sdk/commit/4b5fdcba02c20f26d8b0f07acc87248288522842) Thanks [@christso](https://github.com/christso)! - Fix OAuth error handling for servers
8+
returning errors with HTTP 200 status
9+
10+
Some OAuth servers (e.g., GitHub) return error responses with HTTP 200 status instead of 4xx. The SDK now checks for an `error` field in the JSON response before attempting to parse it as tokens, providing users with meaningful error messages.
11+
12+
- [#1386](https://github.com/modelcontextprotocol/typescript-sdk/pull/1386) [`00249ce`](https://github.com/modelcontextprotocol/typescript-sdk/commit/00249ce86dac558fb1089aea46d4d6d14e9a56c6) Thanks [@PederHP](https://github.com/PederHP)! - Respect capability negotiation in list
13+
methods by returning empty lists when server lacks capability
14+
15+
The Client now returns empty lists instead of sending requests to servers that don't advertise the corresponding capability:
16+
- `listPrompts()` returns `{ prompts: [] }` if server lacks prompts capability
17+
- `listResources()` returns `{ resources: [] }` if server lacks resources capability
18+
- `listResourceTemplates()` returns `{ resourceTemplates: [] }` if server lacks resources capability
19+
- `listTools()` returns `{ tools: [] }` if server lacks tools capability
20+
21+
This respects the MCP spec requirement that "Both parties SHOULD respect capability negotiation" and avoids unnecessary server warnings and traffic. The existing `enforceStrictCapabilities` option continues to throw errors when set to `true`.
22+
23+
- [#1279](https://github.com/modelcontextprotocol/typescript-sdk/pull/1279) [`71ae3ac`](https://github.com/modelcontextprotocol/typescript-sdk/commit/71ae3acee0203a1023817e3bffcd172d0966d2ac) Thanks [@KKonstantinov](https://github.com/KKonstantinov)! - Initial 2.0.0-alpha.0
24+
client and server package

0 commit comments

Comments
 (0)