Expose zod for SDK consumers to avoid version compatibility issues

[jmandel]

When building MCP tools, consumers need zod for input schemas but get type errors due to version mismatches with the SDK's internal zod dependency.

Problem:

import { z } from 'zod'; // Consumer's version (3.23.8)
server.registerTool('tool', {
  inputSchema: z.string() // Type error - incompatible with SDK's zod 3.25.76
});

Error: Type 'ZodString' is missing properties "~standard", "~validate"

Solutions

Option 1: Re-export from main index

// src/index.ts
export { z } from 'zod';

Usage: import { z } from '@modelcontextprotocol/sdk'

Option 2: Move zod to peerDependencies
Force consumers to install compatible zod version themselves.

Recommendation: Option 1 - simpler, no breaking changes, consumers get exact same zod version as SDK.

[fa-lesley]

I was attempting to use zod 4 in my project, which is not compatible. Agree with approach that exports the SDK's version of zod, but also support a zod 4 upgrade.

[jmandel]

Agree (zod 4 upgrade is a different/bigger issue, but important for many reasons)

[MikePresman]

bump, please handle it as such that the correct Zod becomes a peer dependency, this was confusing