Connect Vercel MCP to your AI agents, securely.
One secured endpoint for every Vercel call your AI agents make, scoped per user, inspected, and logged.Try Vercel MCP now
What your agents can ask once Vercel MCP is connected.
“Show me the latest deployments for my project”
“Get the build logs for the most recent failed deployment”
“List all my Vercel projects and their domains”
“Why did this deployment fail?”
“Show the runtime errors from the last hour”
“How do I configure a rewrite in Vercel?”
Select the tools your AI agents can call
248 tools from the Vercel MCP schema.
Showing 248 tools
What Vercel MCP exposes
Vercel MCP groups its 248 tools into 19 categories, each with a suggested starting policy.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Projects | Project and team listing, project details and settings, creation, updates, domains, deployment protection, pausing and transfers | Read / Write | Limit to intended teams |
| Deployments | Deployment listing, details, events, files and feature flags, creation, cancellation, and deploying from inline files or a Claude Design bundle | Read / Write | Require approval before deploying |
| Logs | Build logs, runtime logs and error clusters, observability queries and traces, and log drains | Read / Write | Treat log output as potentially sensitive |
| Access & Fetch | Temporary bypass links and fetching protected deployment URLs | Read / Write | Approve bypass link creation; links grant access to protected deployments |
| Docs & Analytics | Vercel documentation search, Vercel CLI access, feedback to Vercel, and Web Analytics queries and aggregates | Read / Write | Allow documentation and analytics lookups |
| Teams & Access | Teams, members, the authenticated user, user events and access groups with their members and projects | Read | Read-only; member lists hold personal data, so limit to administrators |
| CI & Agent Runs | Vercel CI invocations, attempts, job and task definitions, runs and logs, retries, and agent runs with their traces | Read / Write | Mostly read-only; logs can contain secrets, and retries start new CI work |
| Billing & Purchases | Domain purchase quotes, domain registration and orders, FOCUS billing charges and contract commitments | Read / Write | buy_domain charges the team; present the quote and get explicit approval first |
| Caching & Storage | Remote Caching status and artifacts, cache invalidation by tag or source image, and Blob stores | Read / Write | Invalidation purges cached content for live traffic; approve it |
| Releases & Checks | Rolling releases and their configuration, production promotion and rollback, and re-requesting checks | Read / Write | Promotion, rollback and rolling release stages move production traffic; require approval |
| Domains & DNS | Domains and their configuration, availability and pricing, DNS records, certificates, TLDs, domain orders and domain purchases | Read / Write | Domain purchases charge the team and DNS replacement can take a site offline; require approval |
| Secrets & Environment Variables | Project and shared environment variables, custom environments, and KMS issuers, policies and signing keys | Read / Write | Some tools return decrypted secret values; restrict tightly and approve key revocation |
| Feature Flags | Flags, flag versions, segments, project and team flag settings and SDK keys | Read / Write | Flag updates change live behaviour; SDK keys are credentials |
| Firewall & Security | Firewall configuration, active attack status, attack challenge mode and system bypass rules | Read / Write | Firewall changes can block legitimate traffic or remove protections; require approval |
| Global Config | Global Configs, their items, tokens and backups, with creation, batch item updates and backup restore | Read / Write | Config items are read by live deployments; approve item updates and restores |
| Integrations | Integration configurations, their products and billing plans, webhooks and linked Git repositories | Read | Read-only; allow for inventory |
| Routing & Networking | Routing rules and their versions, aliases, bulk redirects, URL protection bypass, network connectors and microfrontends configuration | Read / Write | Routing and redirect changes affect live traffic; approve promotions and bypass updates |
| Sandboxes | Named sandboxes and their sessions, commands and logs, files and directories, snapshots, timeouts and network policies | Read / Write | Sandbox commands run arbitrary code; approve command execution and network policy changes |
| Toolbar Comments | Vercel Toolbar comment threads, replies, message edits, reactions and resolve status | Read / Write | Replies and edits are visible to teammates; review before posting |
Connect Vercel MCP to your AI agent
Four steps, under ten minutes.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Vercel
Find Vercel in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
Permissions down to the single tool
You do not allow Vercel MCP or block it. You allow the exact tools each agent can call, one by one.
| Vercel MCP | 248 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 248 tools |
- Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
- Default denyA tool you have not enabled is never exposed to the agent.
- Approval on writesTools that change or delete things can require a human to confirm.
Is Vercel MCP secure?
One endpoint instead of raw credentials. Every call is checked against policy and logged.
| AI agentsConnect through your MCP client configuration. | NeuralTrustApply controls based on your configuration. | Vercel MCP248 documented tools. Availability depends on server configuration, client support and team or project scope, and some connections expose a smaller workflow tool list. |
|---|---|---|
| Coding assistants | Connection & credentialsper user | Domains & DNS28 tools |
| Internal copilots | Tool access policiesdeny by default | Routing & Networking26 tools |
| Workflow automations | Request & response inspectioninline | Sandboxes23 tools |
| Compatible MCP clients | Activity monitoringalerts and logs | All other tools171 tools |
Use Vercel MCP with any AI agent framework
Setup guides for the tools your team already uses.
- Claude CodeSetup guide
- CursorSetup guide
- CodexSetup guide
- WindsurfSetup guide
- Gemini CLISetup guide
- Google AntigravitySetup guide
- GitHub CopilotSetup guide
- Claude EnterpriseSetup guide
- Microsoft Copilot StudioSetup guide
- Open WebUISetup guide
- LangChainSetup guide
- HaystackSetup guide
- Strands AgentsSetup guide
- Vercel AI SDKSetup guide
- n8nSetup guide
Common questions about running Vercel MCP through TrustGate.
Other MCP servers
More servers from the catalog.
Cloudflare Workers Bindings
Securely connect your AI agents to Cloudflare Workers Bindings through TrustGate: KV namespaces, R2 buckets, D1 databases, Hyperdrive and Workers, scoped per agent and logged.
24 toolsViewGitHub
Securely connect your AI agents to GitHub through TrustGate: repositories, issues, pull requests, Actions, and 92 more tools, scoped per agent and logged.
96 toolsViewGoogle Cloud Run
Securely connect your AI agents to Google Cloud Run through TrustGate: service listing and details, and deployments from images, source archives or file contents, scoped per agent and logged.
5 toolsView
Connect Vercel MCP instantly
Pick the tools, point your agent at TrustGate, and Vercel MCP is live: scoped, inspected, logged.