fix(mcp): use zod/v3 for compatibility with mcp-handler

[1MoreBuild]

Summary

Fixes #281

• Fix MCP tool get_ai_elements_component not exposing the component parameter in inputSchema
• Use zod/v3 import for backward compatibility with mcp-handler's internal zod-to-json-schema
• Replace z.enum() with z.string().describe() for better schema generation

Problem

The mcp-handler package internally depends on @modelcontextprotocol/sdk@1.22.0, which uses zod-to-json-schema that is incompatible with Zod 4. This caused the component parameter to not be exposed in the tool's inputSchema (empty properties object), resulting in error: MCP error -32603: t._parse is not a function.

Before fix:

{
  "name": "get_ai_elements_component",
  "inputSchema": {
    "properties": {}  // component parameter missing!
  }
}

After fix:

{
  "name": "get_ai_elements_component", 
  "inputSchema": {
    "properties": {
      "component": {
        "type": "string",
        "description": "Component name. Available: artifact, canvas, ..."
      }
    },
    "required": ["component"]
  }
}

Test plan

• Verified tools/list returns correct inputSchema with component parameter
• Verified tools/call for get_ai_elements_component works correctly
• Tested with MCP Inspector using Streamable HTTP transport

[vercel]

Someone is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[haydenbleasel]

Appreciate it @1MoreBuild! 🙏