The MCP server covers deployments, logs, projects, and docs — but there’s no way to read or write environment variables. This is probably the single most useful thing an AI agent could do on Vercel.
Right now, any workflow that needs to rotate a secret, wire up a new integration, or check that preview and production env vars are in sync has to drop out of MCP and fall back to the CLI or REST API.
Adding list_env_vars, get_env_var, set_env_var, and delete_env_var tools (scoped by project and environment) would make the MCP way more practical for real-world automation.