Rebase runs on your own machine — the client starts it, so there is no endpoint to ping. 145 installs a week from npm. Last commit 21 Oct 2026.
Schema, database, document, user and dev-server tools for a Rebase backend project.
We read the source, 3 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const before = new Set(Object.keys(process.env));
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(binary, [...execArgs, "rebase", ...commandArgs], {
import { existsSync, readFileSync, readdirSync, writeFileSync, mkdirSync, chmodSync } from "node:fs";
const before = new Set(Object.keys(process.env));
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const srcDir = path.join(SEED_ASSETS_DIR, assetSubdir);
const text = r < o.drop ? null : r < o.drop + o.mishear ? WRONG[Math.floor(rnd() * WRONG.length)] : word;
COPY package.json pnpm-lock.yaml pnpm-workspace.yaml .npmrc ./
$("tdp-fh").innerHTML = opts; $("tdp-fb").innerHTML = opts;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Rebase and you get told the day something new turns up.
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 rebase -- npx -y @rebasepro/mcp
{
"mcpServers": {
"rebase": {
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
[mcp_servers.rebase]
command = "npx"
args = ["-y", "@rebasepro/mcp"]
{
"mcpServers": {
"rebase": {
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
{
"servers": {
"rebase": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
REBASE_PROJECT_DIR (Project root — the directory holding rebase.json. Defaults to the working directory), REBASE_BASE_URL (Backend URL, used when no local dev server is discovered), REBASE_API_TOKEN (API token for the target project. Not needed against a local dev server), REBASE_MCP_ALLOW_REMOTE_WRITES (Allow destructive tools to run against a non-local target. Off by default).
Database MCP server for schema discovery, comments, and SQL queries.
Local FAISS vector database for RAG with document ingestion, semantic search, and MCP prompts.
Ontology-based MCP server for database schema analysis and RDF/OWL ontology generation
Backend for AI-built apps: database, auth, files, email, AI, payments, deploy, realtime. 170+ tools.
CRM and business database for AI agents: search and update records, documents and workspace schema.
MCP server for one MySQL database: schema, read-only queries and guarded writes.
MCP server for orchestrating Node.js development servers (backend, frontend, databases, etc.)
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Answers built from our own checks of this server.