Vercel MCP fetch returns 302 even with a generated shareable link.

I’m using the connected Vercel integration in ChatGPT to inspect a protected preview deployment.

Project access is authorized, and deployment details and build logs are accessible. However:

web_fetch_vercel_url returns HTTP 302 with “Redirecting…” instead of HTML. get_access_to_vercel_url successfully creates a temporary shareable URL. Passing that exact shareable URL to web_fetch_vercel_url still returns HTTP 302.

The public production URL returns HTTP 200 through the same fetch tool.

Is there a known issue with following authentication redirects or retaining cookies in this tool? How can this be resolved while keeping Deployment Protection enabled?

Vercel’s support assistant directed me here because Vercel MCP support is handled through the community. I’m not technical and would appreciate step-by-step guidance. I can provide deployment identifiers privately if needed.

I’m using the connected Vercel integration in ChatGPT to inspect a protected preview deployment.

Project access is authorized, and deployment details and build logs are accessible. However:

The public production URL returns HTTP 200 through the same fetch tool.

Is there a known issue with following authentication redirects or retaining cookies in this tool? How can this be resolved while keeping Deployment Protection enabled?