Vercel MCP Pro vs Terraform MCP Server

A side-by-side look at the Vercel MCP Pro and Terraform MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Vercel MCP Pro logoVercel MCP ProCloud Platforms · Local subprocess (stdio)Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API60GoodAuth: not declaredTerraform MCP Server logoTerraform MCP ServerCloud Platforms · Remote HTTP/SSEThe official Terraform MCP Server seamlessly integrates with the Terraform ecosystem, enabling provider discovery, module analysis, and direct Registry API integration for advanced Infrastructure as Code workflows.79GreatAuth: api key required

Verdict: choose Vercel MCP Pro for cloud platforms work as a local process; choose Terraform MCP Server for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Vercel MCP Pro logoChoose Vercel MCP Pro when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: VERCEL_TOKEN.
  • You want tools like list_deployments, get_deployment, create_deployment.
Explore Vercel MCP Pro

Terraform MCP Server logoChoose Terraform MCP Server when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
Explore Terraform MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVercel MCP Pro logoVercel MCP ProTerraform MCP Server logoTerraform MCP Server
CategoryCloud PlatformsCloud Platforms
Quality signal60/100 · Good79/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsVERCEL_TOKENNone listed
Verified ownerCommunity listing Verified
GitHub stars01,553
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools70Not listed

Tools & capabilities

Vercel MCP Pro tools 70

  • list_deploymentsList deployments, most recent first. Filter by project, target (production/preview), state, or time window. Use this to see deploy history and find a deployment id.
  • get_deploymentGet full details of one deployment by id or URL (state, build, meta, aliases).
  • create_deploymentCreate a new deployment. The simplest path is to deploy from a connected Git source: pass `name` (project) and a `gitSource` ({ type, repoId/org+repo, ref }). For file-based deploys, provide `files`. For most workflows the /vercel CLI skill is easier — use this when you need API-driven, headless deploys.
  • cancel_deploymentCancel an in-progress (BUILDING/QUEUED) deployment.
  • delete_deploymentDelete a deployment by id (or by URL via the `url` param).
  • get_deployment_eventsGet the build/runtime event log of a deployment (this is where build logs and errors live). Use to diagnose failed builds and runtime bugs. Returns log lines with text, type and timestamps.
  • list_deployment_filesList the file tree of a deployment.
  • get_deployment_file_contentsGet the contents of a single file within a deployment by file id.
  • promote_deploymentPromote an existing deployment to production for a project (instant promotion, no rebuild). This is how you ship a previously-built preview to prod.
  • rollback_deploymentRoll a project's production back to a previous deployment (instant rollback). Pass the deployment id you want to roll back to.
  • get_promote_aliasesCheck the status of the most recent promote/rollback for a project (which aliases were assigned).
  • list_projectsList projects in the account/team. Optionally filter by name or repo.
  • +58 more on the listing page

Terraform MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Vercel MCP Pro

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-mcp-pro": {
      "command": "npx",
      "args": [
        "-y",
        "vercel-mcp-pro"
      ],
      "env": {
        "VERCEL_TOKEN": "YOUR_VERCEL_TOKEN_HERE"
      }
    }
  }
}

Terraform MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hashicorp-terraform-mcp-server": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

Frequently asked questions

Vercel MCP Pro is categorized under Cloud Platforms and uses a local stdio subprocess. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Vercel MCP Pro for cloud platforms work and Terraform MCP Server for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Vercel MCP Pro has no declared pricing — check the project's own site. Terraform MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add vercel-mcp-pro and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Vercel MCP Pro has a quality signal of 60/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.