# Vercel MCP for AI Agents AI Agent Connect > Vercel MCP lets you manage your deployments, projects, and domains through your AI client. Instead of jumping back and forth between the Vercel dashboard and your code, you can check build statuses, pull logs, manage environment variables, and handle custom domains directly in your chat or editor. It's like having a deployment engineer sitting right next to you. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_pzWT8mfyU70G8HGOmLY1PBpKMP7Jb5GpuFhDaQ2I/ai-agent-connect - **Tags:** deployment, frontend-cloud, serverless, git-integration, environment-variables, edge-network ## Description Stop hunting through tabs to see why a production build just failed. This Connector brings your entire Vercel infrastructure into your AI client's reach. You can ask your agent to check the status of the latest deployment, grab the specific logs for a failing build, or find that one environment variable you forgot to add to your staging environment. It handles the tedious bits of deployment management, like listing all your active projects or verifying that your custom domains are actually pointing to the right place. Because Vinkius hosts this Connector, you can connect it to your existing workflow and treat your AI like a dedicated DevOps partner. You'll spend less time copy-pasting IDs and more time actually shipping code. It's about getting the data you need to move faster without the friction of the dashboard. ## Tools ### list_domains List every domain configured for a Vercel team. This includes their verification status and redirect info. ### cancel_deployment Stop a deployment that's taking too long or was started by mistake. It changes the status to CANCELED immediately. ### create_env_var Add a new environment variable to a specific project and target. You can set it for production, preview, or development. ### delete_env_var Remove an old environment variable from a project. Just keep in mind that this action is permanent. ### get_domain Look up the details for a specific custom domain. It shows you the SSL status and DNS verification state. ### get_logs Fetch the runtime logs for a deployment to help debug issues. You can filter by project or specific timestamps. ### list_aliases List all the URL aliases you've mapped to specific deployments. This helps you keep track of your custom links. ### list_deployments See every deployment for an account or a specific project. It shows the status, URL, and git commit info. ### list_env_vars See all the environment variable keys for a project. It hides the actual values to keep your secrets safe. ### list_projects Get a list of all your projects with their framework and git info. It's a great way to see your whole portfolio at once. ### list_teams See all the teams associated with your Vercel account. This is how you get the team IDs needed for other tools. ### get_deployment Pull all the details for a specific deployment ID. Use this to see the exact URL and status of a single build. ### get_project Get the full details for a specific project by its ID or name. It's the quickest way to see project metadata. ### get_user Check the account info for the authenticated user. Use this to make sure your access token is working right. ## Prompt Examples **Prompt:** ``` Did my last production build succeed? ``` **Response:** ``` ### Recent Production Deployments | Status | Time | Commit | URL | | :--- | :--- | :--- | :--- | | **READY** | 2h ago | `main` | [View Deployment](https://example.vercel.app) | **ERROR** | 3h ago | `PR #42` | [View Logs](https://vercel.com/logs) | **BUILDING** | 30m ago | `feature-x` | [View Progress](https://vercel.com/build) The latest production build is **READY**. The previous one failed due to a build timeout. ``` **Prompt:** ``` Add the new stripe key to production. ``` **Response:** ``` Done! I've created the `STRIPE_SECRET_KEY` environment variable for your **production** environment. **Details:** - **Project:** Portfolio Site - **Target:** Production - **Status:** Saved securely This will be available on your next deployment. ``` **Prompt:** ``` Check if my new domain is verified. ``` **Response:** ``` I checked the status for **example.com**: - **Verification:** ✅ Verified - **SSL Status:** ✅ Active (Issued by Let's Encrypt) - **DNS Records:** ✅ Valid A records pointing to Vercel IPs - **Redirects:** None configured Everything looks correct for your custom domain. ``` ## Capabilities ### Check build statuses See if your latest deployment is ready, building, or errored out. ### Fetch runtime logs Pull specific deployment logs to debug issues without leaving your editor. ### Manage environment variables Create, list, and delete keys for different deployment targets. ### Audit custom domains View DNS records, SSL status, and verification states for your domains. ### Track project history Get a high-level view of all projects, frameworks, and git repos. ### Control deployments Cancel running builds or pull specific deployment details on demand. ## Use Cases ### Debugging a failed production build A developer asks the agent to pull logs for a specific deployment ID. The agent uses get_logs to find the error and explains the fix. ### Updating production secrets A developer needs to add a new API key. They tell the agent to use create_env_var for the production environment. ### Checking domain verification A marketer wants to know if the new site is live. The agent uses list_domains and get_domain to check the SSL and DNS status. ### Project auditing A lead wants to see all active projects. The agent uses list_projects to provide a summary of every repo and its latest deployment. ## Benefits - Stop context switching by checking deployment statuses and logs directly in your editor using list_deployments and get_logs. - Manage secrets more safely by using create_env_var and list_env_vars to update production keys without opening the dashboard. - Debug faster by pulling specific deployment details with get_deployment to see exactly why a build failed. - Audit your infrastructure easily by using list_domains and list_projects to see every active project and its health. - Keep your production environment clean by using cancel_deployment to stop unnecessary builds and delete_env_var to prune old keys. ## How It Works The bottom line is you get a command line for your Vercel account inside your AI chat. 1. Subscribe to the Connector and grab your Vercel Access Token from your account settings. 2. Paste the token into your AI client's configuration. 3. Ask your agent to list your projects or check a specific deployment URL. ## Frequently Asked Questions **How does the Vercel MCP help with debugging?** It allows your AI client to pull live runtime logs and deployment details directly into your chat. You can ask it to find specific errors without leaving your editor. **Can I use the Vercel MCP to see my secrets?** You can list the keys and target environments for your variables, but the actual values are hidden for security. You can still create new ones through the agent. **How do I manage my environment variables?** You can ask your agent to add, list, or remove environment variables for specific projects. It handles the creation and deletion for you in plain English. **Can the Vercel MCP check my domain status?** Yes, it can verify if your custom domains are correctly configured, check their SSL status, and view their DNS verification state. **Is it safe to use my Vercel token with an AI client?** Yes, it uses your standard Vercel Access Token to perform actions. You control the permissions and can revoke the token at any time in your Vercel settings. **Can I cancel a build that's taking too long?** Absolutely. You can tell your agent to cancel any running deployment, and it will update the status to CANCELED immediately. **How do I create a Vercel Access Token?** Log in to the [**Vercel Dashboard**](https://vercel.com/account/tokens), go to **Settings > Access Tokens**, click **Create Token**, give it a name, select your team (optional) and scope. Copy the token immediately — it won't be shown again. **Can I manage environment variables via the agent?** Yes! Use `list_env_vars` to see all variable keys (values are hidden for security), `create_env_var` to add new ones with key, value and target environments (production, preview, development), and `delete_env_var` to remove them. **Can I cancel a running deployment?** Yes! Use `cancel_deployment` with the deployment ID to stop a build that is currently in progress. The deployment status will change to CANCELED. You can find the deployment ID from `list_deployments`. **How do I check my deployment history?** Use `list_deployments` optionally filtered by teamId and projectId to see recent deployments. Each entry shows the deployment URL, status (READY, BUILDING, ERROR), framework, git commit and creation date. Use `get_deployment` with a specific deployment ID for full details including build logs.