Cerver runs on your own machine — the client starts it, so there is no endpoint to ping. 228 installs a week from npm.
AI backend for your app: a chat per customer, replies with their cost, spend caps per project.
Today is the operative word: we check Cerver every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cerver -e 'CERVER_KEY=<CERVER_KEY>' -- npx -y @cerver/mcp
{
"mcpServers": {
"cerver": {
"command": "npx",
"args": [
"-y",
"@cerver/mcp"
],
"env": {
"CERVER_KEY": "<CERVER_KEY>"
}
}
}
}
[mcp_servers.cerver]
command = "npx"
args = ["-y", "@cerver/mcp"]
env = { CERVER_KEY = "<CERVER_KEY>" }
{
"mcpServers": {
"cerver": {
"command": "npx",
"args": [
"-y",
"@cerver/mcp"
],
"env": {
"CERVER_KEY": "<CERVER_KEY>"
}
}
}
}
{
"servers": {
"cerver": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cerver/mcp"
],
"env": {
"CERVER_KEY": "<CERVER_KEY>"
}
}
}
}
Put your own value in place of
<CERVER_KEY> (Your Cerver project key (ck_…), from cerver.ai/dashboard).
The author’s registry entry marks it as required.
Connect your own WhatsApp number to Cursor, Claude and ChatGPT: catch up, search, send replies.
Your AI copilot for customer onboarding — projects, KPIs, tasks, and safe writes.
Shared memory for AIs. Share a project with anyone and their AI knows everything yours does.
Set up, test and publish an AI customer support Agent for your SaaS product.
Search published help and hand customer chat to a person. Requires your app's backend integration.
The home for AI-built projects: visitors, restore, publish with a safety check, data backups.
Hosted backend for AI agents: create projects with persistent collections and keys, no signup.
Agent-agnostic persistent memory MCP server. Local-first: memories travel with your project.
Answers built from our own checks of this server.