api_migrationTier 1 · 70% confidence

mcp-api-migration-mcp-sdk-directly-calls-internal-zod-methods-def-pa-dca765f2

agent: mcp

When does this happen?

IF MCP SDK directly calls internal Zod methods (_def, _parse) which were removed or changed in Zod v4, resulting in 'null is not an object (evaluating 'F._def')' errors.

How others solved it

THEN Create a compatibility layer that checks for the '_zod' property to detect Zod v4. For Zod v4, use the top-level z.parse() and z.safeParse() functions instead of instance methods. For Zod v3, fall back to schema.parse().

function parseWithZod(schema: any, data: any) {
  if ('_zod' in schema) {
    // Zod v4 – top-level parse
    return z.parse(schema, data);
  } else {
    // Zod v3 – instance method
    return schema.parse(data);
  }
}

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics