Skip to main content

FrootAI — AmpliFAI your AI Ecosystem Get Started

All servers

Vercel Projects & Deployments

vercel

Search Vercel docs and manage teams, projects, deployments, and logs via the official hosted Vercel MCP server.

Installs
8
Namespace
vercel
Version
hosted
Last attach
reviewed1 months ago

Add to your mcp.json

{
  "mcpServers": {
    "vercel": {
      "type": "sse",
      "url": "https://mcp.vercel.com"
    }
  }
}

Attach in a FrootAI play (fai-manifest)

mcp_scope:
  attached:
    - vercel

Authentication

oauth

no static credential — the AI client performs an interactive OAuth sign-in to your Vercel account on first use (granting the same access as your user); the documentation tools work without authentication.

No credentials required.

Environment variables

No environment variables required.

Sample tools

  • vercel.search_documentation

    Search Vercel documentation for a topic (public, no auth).

  • vercel.list_teams

    List the teams the authenticated user belongs to.

  • vercel.list_projects

    List Vercel projects for a team.

  • vercel.get_project

    Get details for a project — framework, domains, and latest deployment.

  • vercel.list_deployments

    List a project's deployments with state and target.

  • vercel.get_deployment_build_logs

    Get a deployment's build logs to investigate failures.

  • vercel.get_runtime_logs

    Get runtime logs (console output, errors) for a project or deployment.

Destructive-action audit

No destructive tools — audited read-only

Destructive-action audit (X2.18): no tool matches destructive name patterns (destructive_tools is empty); high-impact tools (buy_domain, deploy_to_vercel, toolbar edits) are gated by the trust policy's allowDestructive:false and per-call confirmation.

Known limitations

  • Authenticates via interactive OAuth — the AI client signs in to your Vercel account and gains the same access as your user; the public documentation tools work without auth.
  • Hosted remote endpoint (https://mcp.vercel.com) — requires outbound network access; no local subprocess. Vercel only approves a reviewed list of MCP clients.
  • Some tools take real-world actions — `buy_domain` purchases a domain (charges your account) and `deploy_to_vercel` ships a deployment; enable human confirmation before executing.
  • Tool access mirrors your Vercel permissions; team-scoped tools require a teamId (find it via list_teams or .vercel/project.json).

Spec contributors

Maintainers who landed commits onmcp-specs/vercel.json.

  • pspsbali

Freshness

When this spec was last reviewed by a maintainer and last machine-validated against the live server.

Spec last reviewed
1 months ago(2026-06-25)
Auto-validated
never