We’re experiencing a deployment target mismatch using Vercel MCP’s create_deployment tool.

Our preserved invocation explicitly contains:

requestBody.target: "staging"

However, Vercel created a READY deployment with:

target: "production"

The deployment used the correct isolated project, and the build succeeded. Deployment Protection remains enabled.

We’ve independently verified the MCP arguments and provider response. Unfortunately, the outgoing HTTP request body is unavailable, and the request trace returns 404 trace_not_found.

Could someone from Vercel clarify:

1. Can MCP transform target: "staging" into production?
2. Is this a known issue with custom staging environments or the MCP connector?
3. How can we verify the outgoing request and safely create the intended protected deployment?

We’re working against a hackathon deadline, so any guidance would be appreciated.

We can provide sanitized request IDs and deployment details privately.