You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both packages have a **required peer dependency** on `zod` for schema validation. The SDK internally imports from `zod/v4`, but remains compatible with projects using Zod v3.25+.
36
36
@@ -39,13 +39,13 @@ Both packages have a **required peer dependency** on `zod` for schema validation
Copy file name to clipboardExpand all lines: docs/faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@
14
14
15
15
### Why do I see `TS2589: Type instantiation is excessively deep and possibly infinite` after upgrading the SDK?
16
16
17
-
This TypeScript error can appear when upgrading to newer SDK versions that support Zod v4 (for example, from older `@modelcontextprotocol/sdk` releases to newer `@modelcontextprotocol/sdk-client` / `@modelcontextprotocol/sdk-server` releases) **and** your project ends up with
18
-
multiple `zod` versions in the dependency tree.
17
+
This TypeScript error can appear when upgrading to newer SDK versions that support Zod v4 (for example, from older `@modelcontextprotocol/sdk` releases to newer `@modelcontextprotocol/client` / `@modelcontextprotocol/server` releases) **and** your project ends up with multiple
18
+
`zod` versions in the dependency tree.
19
19
20
20
When there are multiple copies or versions of `zod`, TypeScript may try to instantiate very complex, cross-version types and hit its recursion limits, resulting in `TS2589`. This scenario is discussed in GitHub issue
Copy file name to clipboardExpand all lines: docs/server.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
## Server overview
2
2
3
-
This SDK lets you build MCP servers in TypeScript and connect them to different transports. For most use cases you will use `McpServer` from `@modelcontextprotocol/sdk-server` and choose one of:
3
+
This SDK lets you build MCP servers in TypeScript and connect them to different transports. For most use cases you will use `McpServer` from `@modelcontextprotocol/server` and choose one of:
4
4
5
5
-**Streamable HTTP** (recommended for remote servers)
6
6
-**HTTP + SSE** (deprecated, for backwards compatibility only)
@@ -70,7 +70,7 @@ For more detailed patterns (stateless vs stateful, JSON response mode, CORS, DNS
70
70
MCP servers running on localhost are vulnerable to DNS rebinding attacks. Use `createMcpExpressApp()` to create an Express app with DNS rebinding protection enabled by default:
@@ -201,7 +201,7 @@ See the MCP spec sections on prompts and resources for complete details, and [`s
201
201
202
202
Tools, resources and prompts support a `title` field for human‑readable names. Older APIs can also attach `annotations.title`. To compute the correct display name on the client, use:
203
203
204
-
-`getDisplayName` from `@modelcontextprotocol/sdk-client`
204
+
-`getDisplayName` from `@modelcontextprotocol/client`
0 commit comments