fix: Pass Zod schemas directly to MCP SDK instead of raw JSON Schema

The SDK expects Zod schemas for input validation (calls safeParseAsync).
Passing raw JSON Schema objects broke all tool execution.

Author: limehawk

src/server.ts

@@ -1,39 +1,25 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { z } from "zod";
 import { createRequire } from "module";
 import { allTools } from "./mcp/tools/index.js";
 
 // Import version from package.json
 const require = createRequire(import.meta.url);
 const { version } = require("../package.json");
 
-// Type for MCP tool callback - simplified for raw JSON Schema passthrough
-type McpToolCallback = (
-  args: Record<string, unknown>,
-  extra: unknown
-) => Promise<{ content: { type: "text"; text: string }[]; isError?: boolean }>;
-
 export function createServer() {
   const server = new McpServer({
     name: "dokploy",
     version,
   });
 
   for (const tool of allTools) {
-    // Convert Zod schema to JSON Schema draft-2020-12 for Claude API compatibility
-    // The MCP SDK's default conversion produces draft-07 which Claude API rejects
-    const jsonSchema = z.toJSONSchema(tool.schema, { target: "draft-2020-12" });
-
-    // Use registerTool with raw JSON Schema to bypass SDK's draft-07 conversion
-    // Casts needed because SDK types don't account for raw JSON Schema passthrough
-    server.registerTool(
+    // Pass Zod schema directly - SDK v1.26+ handles both Zod v3 and v4
+    // SDK converts to JSON Schema internally for tool listing
+    server.tool(
       tool.name,
-      {
-        description: tool.description,
-        inputSchema: jsonSchema as unknown as z.ZodRawShape,
-        annotations: tool.annotations,
-      },
-      tool.handler as McpToolCallback
+      tool.description,
+      tool.schema.shape,
+      tool.handler
     );
   }