Vercel
Vercel is a platform for frontend frameworks and static sites, enabling developers to host websites and web services that deploy instantly, scale automatically, and require minimal configuration.
Verdict
Common use cases
- Add secrets to a project before deploy
- Check domain availability for a new site
- Create preview deployment from a branch
- Rotate auth tokens after a security audit
- Verify cache artifacts exist before upload
Integration
- Vendor
- Vercel
- Category
- developer-tools
- Auth
- OAUTH2
- Tools
- 35
- Composio slug
vercel
Tools
- Add Environment Variable
Tool to add an environment variable to a vercel project. use after confirming the project exists and you need to configure secrets or configuration values across environments before deployment. example: "add api key=secret to production".
- Check Cache Artifact Exists
Tool to check if a cache artifact exists by its hash. use when verifying whether a cache artifact is already stored before upload.
- Check Domain Availability
Tool to check if a domain is available for registration. use when you need to verify domain availability before purchase.
- Check Domain Price
Tool to check the price for a domain before purchase. use when evaluating cost and availability prior to domain registration.
- Create Auth Token
Tool to create a new authentication token. use when you need to programmatically generate a new token after validating permissions. example: "create auth token named my-token"
- Create Edge Config
Tool to create a new edge config for a vercel project. use when you need to define edge caching settings before deploying your project across a specified repository.
- Create Edge Config Token
Tool to create a new token for a specific edge config. use when you need a read-only access token after provisioning your edge config.
- Create new deployment
Tool to create a new deployment. use when you need to deploy files or a git commit to a vercel project.
- Delete Auth Tokendestructive
Tool to delete an authentication token. use when you need to revoke a token programmatically after confirming its validity. example: "delete auth token with id abc123"
- Delete Deploymentdestructive
Tool to delete a specific deployment by its unique id. use after confirming the deployment identifier to clean up unused or failed deployments.
- Delete Edge Config Tokensdestructive
Tool to delete tokens associated with a specific edge config. use when you need to revoke one or more access tokens from an existing edge config by its id.
- Delete Environment Variabledestructive
Tool to delete a specific environment variable from a project. use after verifying the correct variable id to remove it.
- Delete Vercel Projectdestructive
Tool to delete a specific project by its id or name. use after confirming the correct project id or name to permanently remove it.
- Deploy Edge Function
Deploy edge functions to vercel. use when you need to deploy serverless functions that run on the edge runtime with fast cold starts and global distribution.
- Get Auth Token Metadata
Tool to retrieve metadata for an authentication token. use when you need to inspect details of a specific token for auditing or debugging.
- Get deployment details
Tool to retrieve detailed information about a specific deployment. use after triggering a deployment and you need to inspect its status and configuration. example: "get details for deployment dpl 123abc".
- Get Deployment Events
Tool to retrieve events related to a specific deployment. use when monitoring or debugging deployment history or streaming real-time events. example: "get events for deployment dpl xxx since 1540095775941."
- Get Deployment Logs
Tool to retrieve logs for a specific vercel deployment. use when monitoring deployment execution, debugging issues, or analyzing deployment performance. example: "get logs for deployment dpl xxx since 1540095775941."
- Get Domain Transfer Info
Tool to get information required to transfer a domain to vercel. use when you need to check transfer availability or current status before initiating a transfer.
- Get Edge Config
Tool to retrieve details of a specific edge config. use when you need to inspect edge config metadata by id before updating or deleting.
- Get Edge Config Item
Tool to retrieve a specific item within an edge config. use after obtaining the edge config id and when you need to inspect or validate a particular configuration item by its key.
- Get Edge Config Token
Tool to retrieve details of a specific token associated with an edge config. use when you need metadata for an existing edge config token.
- Get Vercel Project
Tool to retrieve information about a vercel project by id or name. use when you need project metadata after obtaining its identifier.
- List All Deployments
Tool to list all deployments. use after authenticating to retrieve deployments under your user or team context. example: "list deployments for project qmx...".
- List All Teams
Tool to list all teams accessible to the authenticated user. use after authentication to retrieve their ids and slugs.
- List Auth Tokens
Tool to list authentication tokens. use when you need to retrieve all tokens for the current user or an optional team.
- List Deployment Checks
Tool to retrieve a list of checks for a specific deployment. use after a deployment to inspect check statuses and results.
- List Edge Config Items
Tool to retrieve a list of items within a specific edge config. use when you need to inspect or manage all key–value items after creating an edge config.
- List Edge Configs
Tool to list all edge configs. use when you need to enumerate all edge config definitions for your account or team.
- List Edge Config Tokens
Tool to retrieve a list of tokens for a specific edge config. use after obtaining an edge config's id to list its tokens.
- List Environment Variables
Tool to list environment variables for a specific project. use when you need to inspect or page through the environment settings before deployment.
- List Vercel Aliases
Tool to list all aliases for the authenticated user or team. use when you need to retrieve aliases filtered by various criteria.
- Update Edge Config
Tool to update an existing edge config. use when you need to rename the slug of an edge config for reorganization or migration purposes. only the slug field may be updated; ensure you confirm the new slug before using.
- Update Edge Config Items
Tool to update items within a specific edge config. use when you need to batch modify, add, or remove key-value pairs in an existing edge config.
- Update Vercel Project
Tool to update an existing project. use when you need to modify a vercel project’s configuration before deployment. use after confirming the project id or name.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration' and select Vercel from the developer tools category. 3. You'll be redirected to Vercel's OAuth consent screen — sign in with the account that owns your team or projects. 4. Grant the requested scopes: read and write access to deployments, projects, environment variables, domains, and edge configs. 5. Vercel redirects you back to Switchy with a success confirmation. 6. Open any Project in your workspace and type '@Vercel check deployment status for my-app' to test the connection. 7. If the MCP returns deployment details, you're ready to invoke any of the 35 tools by @mentioning Vercel in your prompts.
What teammates see: by default, memories from Vercel are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add Environment Variable
@Vercel add an environment variable named DATABASE_URL to the my-app project for production and preview environments
Check Domain Price
@Vercel check the price and availability for the domain myapp.dev
Create New Deployment
@Vercel create a new deployment for the my-app project from the main branch
Create Auth Token
@Vercel create an auth token named ci-pipeline-token with read and write permissions
Create Edge Config
@Vercel create an edge config named feature-flags for the my-app project linked to the GitHub repo myorg/myapp
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@vercel list all deployments for my-app in the last 7 days and show their status
Found 12 deployments for 'my-app' in the past week: • prod-abc123 (main branch) — READY — deployed 2 hours ago • preview-def456 (feature/auth) — READY — deployed 1 day ago • preview-ghi789 (fix/layout) — ERROR — failed 3 days ago • prod-jkl012 (main branch) — READY — deployed 4 days ago Most recent production deployment is running at my-app.vercel.app. The failed preview deployment encountered a build error in the CSS compilation step.
This example shows the MCP's read capability for deployment history. Requires OAuth scope to access project metadata. Response format varies by project configuration — some teams have hundreds of preview deployments, so consider filtering by branch or status to keep output manageable.
@vercel add environment variable DATABASE_URL to my-app for production and preview environments
Environment variable 'DATABASE_URL' added successfully to project 'my-app': • Target environments: Production, Preview • Variable type: Encrypted • Created: just now This variable will be available in your next deployment. Existing deployments will not automatically pick up this change — trigger a new deployment or redeploy to apply the updated configuration.
Demonstrates the MCP's write capability for project configuration. This action immediately modifies your Vercel project settings and affects future deployments. Requires project-level write permissions via OAuth. Be cautious with sensitive values — confirm the variable name and scope before execution to avoid exposing secrets to unintended environments.
@vercel check if domain my-startup.com is available and show me the registration price
Domain availability check for 'my-startup.com': • Status: Available for registration • Price: $12.00 USD/year • Registrar: Vercel Domains (powered by partner registrar) This domain can be purchased and automatically configured with your Vercel project. Registration includes DNS management and SSL certificate provisioning. Note that domain availability can change quickly — verify again immediately before purchase if you're ready to proceed.
Shows the MCP's ability to query external domain registration services through Vercel's API. Useful for validating domain ideas before committing to infrastructure setup. Pricing may vary by TLD and promotional periods. This is a read-only check — actual purchase requires a separate action and billing confirmation.
Use-case deep-dives
When Vercel MCP speeds up frontend iteration cycles
A 5-person design-eng team ships landing pages every two weeks. They run daily design reviews where the PM and designer need to see live previews of three competing hero variants. The Vercel MCP wins here because the engineer can trigger preview deployments from chat during the review call, then share the URLs in Slack without context-switching to the Vercel dashboard. The MCP's "Create new deployment" tool takes a git commit SHA and returns a live URL in under 30 seconds. This works until you're deploying more than 15 previews a day—at that scale, the OAuth token refresh overhead starts to add latency, and you're better off scripting the Vercel CLI directly. If your team reviews work synchronously and deploys fewer than a dozen previews daily, this MCP cuts 2-3 minutes per review.
When this MCP helps support triage DNS issues faster
A 3-person support team at a white-label SaaS handles 20-30 custom domain tickets a week. Customers report "domain not working" and support needs to check availability, verify DNS records, and confirm the domain isn't already claimed. The Vercel MCP's "Check Domain Availability" and domain price tools let the support agent answer the customer's question in chat without opening the Vercel dashboard or asking engineering. The trade-off: if your support team doesn't already use Switchy for ticket triage, the setup cost (OAuth, scopes, training) outweighs the 90-second time save per ticket. This MCP makes sense when support is already in Switchy and handles at least 10 domain questions a week. Below that threshold, a shared Vercel login is faster.
When environment variable changes justify the MCP overhead
A 6-person backend team deploys a Next.js API to Vercel. They discover a misconfigured Stripe webhook URL in production at 9pm on a Friday. The on-call engineer needs to update the environment variable and redeploy without waiting for CI or asking the DevOps lead for dashboard access. The Vercel MCP's "Add Environment Variable" tool lets the engineer fix the config from chat, then trigger a redeployment with "Create new deployment" in under two minutes. The boundary: if your team makes fewer than two emergency config changes a month, the OAuth setup and token management aren't worth it—just give the on-call rotation dashboard access. This MCP pays off when you're making 5+ env var changes a week and want audit logs in chat instead of scattered across Vercel's UI.
Frequently asked
What does the Vercel MCP let me do in Switchy?
It gives your AI assistant direct control over your Vercel projects — deploying code, managing environment variables, checking domain availability, creating auth tokens, and configuring edge caching. Instead of switching to the Vercel dashboard or running CLI commands, you can ask your assistant to deploy a branch, add a secret, or verify a cache artifact exists.
Do I need admin access to connect Vercel via OAuth?
Yes. The OAuth flow requires you to authorise Switchy with permissions to read and write deployments, environment variables, domains, and edge configs across your Vercel account. If you're not an account owner or don't have deployment rights on the relevant projects, the connection will fail or tools will error out when invoked.
Can the Vercel MCP roll back a deployment or manage preview URLs?
It can create new deployments from files or Git commits, but it doesn't expose a dedicated rollback tool. To revert, you'd ask the assistant to redeploy an earlier commit hash. Preview URLs are generated automatically by Vercel when you deploy a branch — the MCP doesn't manage them separately, but your assistant can trigger the deployment that creates one.
Why use this instead of the Vercel CLI or dashboard?
Use the MCP when you want your AI assistant to handle deployment steps inline with other tasks — like fetching logs from Datadog, updating a Notion doc, then deploying the fix to Vercel, all in one conversation. If you're already scripting with the CLI or prefer the dashboard's visual feedback, stick with those.
Who on the team should connect the Vercel account?
Whoever owns the Vercel account or has admin rights to the projects you want to deploy. Once connected in Switchy, any team member with access to that workspace can ask the assistant to use Vercel tools — so limit workspace membership if you don't want everyone triggering production deployments.