vercel vs Percher
vercel is a plugin bundle for AI coding tools published by vercel. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Claude Code: claude-plugins-community). Percher is an MCP server published by percher.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  vercel | |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.50.0 Forks (GitHub): 65 Stars (GitHub): 303 Not marked · First seen |
Not listed |
| Copilot CLI: github/awesome-copilot | Listed Version: 0.48.1 Forks (GitHub): 65 Stars (GitHub): 303 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 0.47.0 Forks (GitHub): 65 Stars (GitHub): 303 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (npm): 1 602 Downloads/week (npm): 93 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 | vercel | Percher |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 303 | No figure on GitHub |
| Forks (GitHub) (differs) | 65 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (mcp.vercel.com) | Remote server (mcp.percher.app/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 48 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/vercel/vercel-plugin | Not stated |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 24 h ago |
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
vercel
Vercel deployment platform integration. Manage deployments, check build status, access logs, configure domains, and control your frontend infrastructure directly from Claude Code.
Percher
MCP-native hosting: publish and operate AI-built web apps live at name.percher.run.
How to run each
vercel As a Claude Code plugin
/plugin install vercel@claude-plugins-officialPercher As a remote MCP server
claude mcp add --transport http percher https://mcp.percher.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Percher has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: vercel · What it can do: Percher · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.