Compared · Infra & deploy · Cursor

Best MCP servers for Infra & deploy in Cursor

10 entries in the AgentTask Atlas catalog fit infra & deploy and have Cursor setup instructions in their official README or docs. Cursor reads MCP servers from mcp.json (per project or global) and from its Marketplace. For infrastructure work the choice is mostly about where you deploy and how much of your cloud account you are willing to hand to the agent: every entry below acts with your own account, CLI login or token.

Based on official docs, not hands-on tested. Cursor steps checked 2026-10-20; catalog entries verified 2026-10-16 to 2026-10-21. Not ranked by a score: entries that document more clients come first.

Hosted (remote URL) option: Vercel MCP, Prisma MCP Server, AWS MCP Servers, Neon MCP Server, Supabase MCP, Cloudflare MCP servers.
Runs locally (npx, uvx, Docker, binary or CLI): Heroku Platform MCP Server, Netlify MCP Server, Terraform MCP Server, Docker MCP Gateway.
Credentials optional or depend on what you enable: Terraform MCP Server, Docker MCP Gateway; every other entry needs an account login, OAuth grant, key or cloud identity.

Name	Hosted	Credentials	License	Verdict
Vercel MCP Vercel	Yes	Required	Not stated (hosted service, no public source repository)	Pick it to inspect deployments and logs or manage Vercel projects from the agent; it acts with your account's access, so keep human confirmation on for changes.
Prisma MCP Server Prisma	Yes	Required	Not stated (hosted service, no public source repository)	Pick it if you run Prisma Postgres or Prisma Compute and want the agent to query data, check backups or read deploy logs; review every destructive approval, it acts on live resources.
AWS MCP Servers AWS Labs	Yes	Required	Apache-2.0	Pick the specific AWS server you need; the docs server needs no credentials, others use your IAM profile.
Heroku Platform MCP Server Heroku	—	Required	Apache-2.0	Pick it to manage Heroku apps from the agent; the README recommends `heroku mcp:start` so you don't expose an API key.
Netlify MCP Server Netlify	—	Required	NOASSERTION	Pick it to build and deploy Netlify sites from the agent; it authenticates with your Netlify account.
Terraform MCP Server HashiCorp	—	Optional	MPL-2.0	Pick it for Terraform Registry lookups; add TFE_TOKEN only if you need HCP Terraform workspaces.
Docker MCP Gateway Docker	—	Optional	MIT	Pick it to run several MCP servers in containers; permissions depend on the servers you enable.
Neon MCP Server Neon	Yes	Required	MIT	Pick it to manage Neon branches and run SQL; it acts with your account's rights.
Supabase MCP Supabase	Yes	Required	Apache-2.0	Pick it for Supabase SQL and migrations; use the documented read-only and project-scoped modes.
Cloudflare MCP servers Cloudflare	Yes	Required	Apache-2.0	Pick it for Workers, observability and Cloudflare docs; each remote server uses its own OAuth scopes.

How to add them to Cursor

1. Pick project or global config
Project servers go in .cursor/mcp.json inside the repository (good for a team that deploys the same project). Global servers go in ~/.cursor/mcp.json and are available in every project.
2. Add a hosted (remote) server
Remote servers only need their URL in Cursor's format. This is the snippet from Vercel's own Cursor instructions; after saving, Cursor tries to connect and shows a Needs login prompt; click it to authorize Cursor to access your Vercel account. The other remote URLs are in the install notes below.
```
{
  "mcpServers": {
    "vercel": {
      "url": "https://mcp.vercel.com"
    }
  }
}
```
3. Add a local server that runs a command
Local servers start a process on your machine. Netlify's README gives this config for MCP config files (it needs Node.js 22 or higher and a Netlify account):
```
{
  "mcpServers": {
    "netlify": {
      "command": "npx",
      "args": [
        "-y",
        "@netlify/mcp"
      ]
    }
  }
}
```
4. Prefer your existing CLI login over API keys
Heroku's README has a Cursor example that reuses your Heroku CLI login through heroku mcp:start (CLI 10.8.1 or later), so no API key sits in the file:
```
{
  "mcpServers": {
    "heroku": {
      "command": "heroku mcp:start"
    }
  }
}
```
5. If a server needs a token, keep it out of the file
Cursor resolves ${env:NAME} in command, args, env, url and headers, so a token can come from your shell environment instead of being committed with .cursor/mcp.json.
```
{
  "mcpServers": {
    "remote-server": {
      "url": "https://api.example.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MY_SERVICE_TOKEN}"
      }
    }
  }
}
```
6. Keep tool approval on for changes
Cursor asks for approval before running MCP tools by default; click the arrow next to the tool name to see its arguments before you approve a deploy, migration or delete. MCP tools follow the same Run Modes as terminal commands, so check your Run Mode before allowlisting infra tools.
7. Debug a server that won't connect
Open the Output panel (Cmd+Shift+U) and select MCP Logs for connection, authentication and crash errors. Toggle a server off from Customize in the sidebar without deleting its config.

One-click installs exist for some of these: Vercel's docs and the Netlify and Heroku READMEs have an Add to Cursor button, and the Cursor Marketplace offers one-click install with OAuth.
Cursor's stdio field reference lists "type": "stdio"; the vendor snippets above are copied as the vendors publish them.
envFile is only available for stdio servers; remote (HTTP/SSE) servers use ${env:...} interpolation instead.
Team admins can distribute MCP servers through a team marketplace, and Enterprise admins can allowlist servers by command or URL pattern and restrict which tools run automatically.

Full walkthrough for any server: How to add an MCP server to Cursor.

Install notes and account access

Servers that log in to a vendor account act on real data and resources. The permissions line is what the vendor says the server can do with your account.

Vercel MCP · Vercel: Connect to https://mcp.vercel.com. Claude Code: `claude mcp add --transport http vercel https://mcp.vercel.com`, then `/mcp` to authenticate; or `npx add-mcp https://mcp.vercel.com` to configure detected clients (see docs). official docs ↗
Can do: Searches Vercel docs, manages projects and deployments, reads deployment logs and queries Web Analytics; Vercel says connecting grants the AI the same access as your Vercel user account (limited by the OAuth grant and team permissions).
Credentials: Vercel account OAuth (explicit consent for each client connection). · Maintenance: Hosted remote server; official docs last updated 2026-09-15; no public source repository or GitHub release · Verified 2026-10-20
Prisma MCP Server · Prisma: Connect to https://mcp.prisma.io/mcp (Streamable HTTP). Claude Code: `claude mcp add --transport http prisma https://mcp.prisma.io/mcp`; Gemini CLI: `gemini mcp add --transport http Prisma https://mcp.prisma.io/mcp --scope user` (see docs for other clients). official docs ↗
Can do: Manages Prisma Postgres databases (create, run SQL, restore backups), Prisma Compute deployments (logs, environment variables), Object Storage buckets and access keys, and searches Prisma docs in the workspace you approve; Prisma warns that tools that change or delete resources can cause data loss.
Credentials: Prisma Console account sign-in (OAuth), then pick a workspace and approve access. · Maintenance: Hosted remote server; official docs last updated 2026-09-22; the old prisma/mcp repo is archived; no GitHub release · Verified 2026-10-21
AWS MCP Servers · AWS Labs: Pick a server from the README table, e.g. `uvx awslabs.aws-documentation-mcp-server@latest`, or the remote AWS MCP Server (preview) via `mcp-proxy-for-aws`. official docs ↗
Can do: Each server acts on AWS with your local credentials/profile; scope depends on the IAM role.
Credentials: AWS credentials (profile / IAM) for servers that call AWS; docs server needs none. · Maintenance: Release 2026.10.20261015170211 on 2026-10-16; last commit 2026-10-16 · Verified 2026-10-16
Heroku Platform MCP Server · Heroku: Run `heroku mcp:start` from your client's MCP config, or `npx -y @heroku/mcp-server` with HEROKU_API_KEY (see README). official docs ↗
Can do: Manages Heroku apps, add-ons and resources with your Heroku CLI identity.
Credentials: Heroku CLI login (`heroku mcp:start`) or HEROKU_API_KEY. · Maintenance: Release mcp-server-v1.2.12 on 2026-10-12 · Verified 2026-10-16
Netlify MCP Server · Netlify: Add `npx -y @netlify/mcp` to your client's MCP config (see README). official docs ↗
Can do: Creates, deploys and manages sites in your Netlify account.
Credentials: Netlify account login; a Personal Access Token only as a temporary auth workaround, as documented. · Maintenance: Release mcp-v1.19.0 on 2026-10-13 · Verified 2026-10-16
Terraform MCP Server · HashiCorp: Docker image hashicorp/terraform-mcp-server or released binary (see README). official docs ↗
Can do: Queries Terraform Registry; with a token, works with HCP Terraform/TFE workspaces.
Credentials: Optional TFE_TOKEN for HCP Terraform / Enterprise features. · Maintenance: Release v1.3.0 on 2026-08-26; last commit 2026-10-15 · Verified 2026-10-16
Docker MCP Gateway · Docker: Docker Desktop MCP Toolkit or `docker mcp gateway run` (see README). official docs ↗
Can do: Runs other MCP servers in containers on your machine; permissions depend on the servers you enable.
Credentials: Depends on each enabled server (secrets managed by Docker). · Maintenance: No GitHub release; last commit 2026-09-16 · Verified 2026-10-16
Neon MCP Server · Neon: `npx neon@latest init`, or add the remote server with `npx add-mcp https://mcp.neon.tech/mcp` (see README). official docs ↗
Can do: Manages Neon projects, branches and runs SQL with your account's rights.
Credentials: Neon OAuth (remote) or NEON_API_KEY. · Maintenance: No GitHub release; last commit 2026-10-15 · Verified 2026-10-16
Supabase MCP · Supabase: Remote https://mcp.supabase.com/mcp (see README for flags like read_only and project_ref). official docs ↗
Can do: Manages Supabase projects: SQL, migrations, branches, edge functions; read-only and project-scoped modes documented.
Credentials: Supabase OAuth (remote) or a personal access token. · Maintenance: Release mcp-server-supabase-v0.14.0 on 2026-10-14; last commit 2026-10-16 · Verified 2026-10-17
Cloudflare MCP servers · Cloudflare: Add a remote URL like https://docs.mcp.cloudflare.com/mcp or https://observability.mcp.cloudflare.com/mcp (list in README). official docs ↗
Can do: Remote servers act on your Cloudflare account (Workers, observability, DNS analytics, docs) per OAuth scopes.
Credentials: Cloudflare OAuth (per server). · Maintenance: Release containers-mcp@0.2.19 on 2026-08-11; last commit 2026-10-09 · Verified 2026-10-16

Sources

All infra & deploy entries, in every client: Best MCP servers for Infra & deploy · Infra & deploy explorer. Ask the catalog from inside Cursor with the free, read-only AgentTask Atlas MCP server.

Other comparisons: Best MCP servers for Debugging & observability in Cursor · Databases & SQL · Debugging & observability · Library docs & research · Web fetching & scraping · Frontend & UI · Local files · Docs & writing

⚠ No independent security audit: entries summarize official sources only. Review permissions and code before installing.

Best MCP servers for Infra & deploy in Cursor

How to add them to Cursor

1. Pick project or global config

2. Add a hosted (remote) server

3. Add a local server that runs a command

4. Prefer your existing CLI login over API keys

5. If a server needs a token, keep it out of the file

6. Keep tool approval on for changes

7. Debug a server that won't connect

Install notes and account access

Sources