Vercel Alternative MCP. Audit deployments and domains from your chat window.

This MCP server gives your AI agent full control over your Vercel deployment pipeline without you ever touching a dashboard. You'll use this to manage everything—from custom domains to live build logs—just by chatting with your agent. Forget context switching; your AI client handles the devops grunt work.

Project and Team Oversight

You can start by seeing every single project associated with your account using list_projects. This tool lists out all available Vercel projects, showing their ID, what framework they use, where they point to in Git, and the status of their last deployment. If you need deeper details on one specific setup, get_project pulls all the metadata for that project, including which team owns it and its framework type.

If you manage multiple teams under your account, list_teams retrieves a list of every team ID and slug. And if you just need basic confirmation of who’s connected, get_user spits out the core details about your Vercel account user.

Deployment Lifecycle Management

Tracking deployments is straightforward. You can use list_deployments to see every deployed application instance in your whole account or just a specific project. This list shows you the build status and commit details for all of them. If you need the full story on one particular build, get_deployment pulls all the status details for that single deployment ID, giving you its permanent URL and what commit it’s running from.

You don't want a build hanging forever? You can stop any running process immediately by providing the deployment ID to cancel_deployment. It forces the termination of those builds. Furthermore, list_aliases shows every custom URL (alias) you’ve pointed at a project, mapping those public URLs directly to their corresponding deployments.

Debugging and Logging

When things break, you need logs fast. To grab detailed runtime history for any deployment, use get_logs. This tool lets you fetch historical logs using timestamps or by filtering against a specific project ID, which is essential when figuring out what went wrong hours ago. If the issue relates to a single build that failed, you rely on list_deployments first, and then drill down with get_deployment before fetching those critical logs.

Environment Variables Control

Managing secrets shouldn't be a hassle. Your agent handles it: use create_env_var to add or update an environment variable—like setting up a staging API key—for a project, letting you target one or more specific environments at once. If you need to clear out old keys, delete_env_var removes an existing variable using its unique ID.

You can check which variables are already set on a project without seeing the actual sensitive values by calling list_env_vars.

Domain and SSL Auditing

For your custom domains, you've got two tools. First, list_domains shows every domain configured for a team, giving you its verification state and the current status of its SSL certificate right off the bat. If you need the deep technical details—like what DNS records are set up or if the SSL cert is actually validated—you call get_domain.

This pulls the full configuration for any custom domain name you're running.