Vercel MCP server
Vercel in any MCP client, through Memtro: Vercel does not publish this server. Memtro's Vercel connector reads Vercel through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read-only Vercel: projects with their production state, deployment history by project/branch/outcome, one deployment with its build log (errors first), domains, and teams. Environment variables are never read.
Reads
vercel_projectsList Vercel projects in the connection's scope (optionally filtered by name) with framework, linked repository…vercel_deploymentsDeployment history, newest first: filter by project (name or id), target (production/preview), state (READY, ERROR, BUILDING, CANCELED, QUEUED)…vercel_deploymentOne deployment by id (dpl_…) or hostname (my-app-abc123.vercel.app) with its state, commit, aliases…vercel_domainsDomains: with project, the domains assigned to that project (verified, redirects, branch); without…vercel_teamsTeams the token's account belongs to (id, slug, name, role) and which scope this connection queries.
Connect it
First connect Vercel on Dashboard → Connections, then add Memtro to your client once. The Vercel tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
One command registers the server; the tools are then available in every session.
claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
--header "Authorization: Bearer sk-memtro-..."Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Vercel connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What is deployed to production for the marketing site right now?
- › Why did the last deploy of the dashboard fail?
- › Show failed builds this week across all projects
- › Which domains on the web project are not verified?
- › How many production deploys did the API project have yesterday?
Questions
- Is this an official Vercel MCP server?
- No. It is Memtro's MCP server with Memtro's Vercel connector behind it: the connector reads Vercel through its API with the credentials you connect on Dashboard → Connections, and Vercel publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Vercel?
- Not yet. Today every Vercel tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.