Render vs Vercel MCP Pro
Render is an MCP server published by render-oss. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vercel MCP Pro is an MCP server published by helbertparanhos. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Render |  Vercel MCP Pro |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:96ee41e6433a Forks (GitHub): 97 Pulls (Docker Hub): 15 906 Stars (Docker Hub): 1 Stars (GitHub): 180 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 537 Downloads/week (npm): 69 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Render | Vercel MCP Pro |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 180 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 15 906 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 97 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/render) | On your machine (vercel-mcp-pro) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 24 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/render-oss/render-mcp-server | github.com/helbertparanhos/vercel-mcp-pro |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Render
Interact with your Render resources via LLMs.
Vercel MCP Pro
Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API
How to run each
Render As a local MCP server: Docker image
claude mcp add --env "RENDER_API_KEY=<YOUR_RENDER_API_KEY>" --transport stdio render -- docker run -i --rm -e RENDER_API_KEY mcp/renderRequires: RENDER_API_KEY (secret)
Vercel MCP Pro As a local MCP server: npm package
claude mcp add --env "VERCEL_TOKEN=<YOUR_VERCEL_TOKEN>" --transport stdio vercel-mcp-pro -- npx -y vercel-mcp-proRequires: VERCEL_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Vercel MCP Pro publish no list of tools, so we do not compare tools.
Settings each asks for
Only Render asks for
RENDER_API_KEY (secret)
Only Vercel MCP Pro asks for
VERCEL_READONLYVERCEL_TEAM_IDVERCEL_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Render · What it can do: Vercel MCP Pro · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.