Rebase logo

Rebase

Manage Rebase schemas, PostgreSQL databases, documents, users, storage, branches, and development servers through MCP.

Install Rebase

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Rebase, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

Rebase MCP server exposes agent tools for managing a Rebase backend project, including schema generation, PostgreSQL migrations, document CRUD, users, roles, storage, and development-server controls. It works with Rebase collection definitions and generated Drizzle schemas, and can inspect or modify the connected database. Database branch management and some schema operations are restricted to administrators, while destructive changes require an explicit human-controlled CLI step. Reach for Rebase when an agent needs to maintain a Rebase project or operate its backend data without switching between separate development tools.

Use cases

  • Generate Drizzle schemas from collection definitions
  • Preview and apply Rebase database changes
  • Manage documents and users in a Rebase backend
  • Inspect and switch development database branches
  • Start and troubleshoot the Rebase development server

Key features

  • Collection-to-Drizzle schema generation
  • PostgreSQL introspection and migration management
  • Document, user, role, and storage administration
  • Database branch lifecycle controls
  • Typed JavaScript and TypeScript SDK generation
  • Rebase development-server controls

Tools42

What Rebase lets your agent do. Expand a tool for its parameters.

Verified live~2.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

11/11 checks healthy over the last 54d

What it can do

From the 42 tools this server returned when we ran it.

Can delete or modify data · 7Handles credentials · 2Makes network requests · 3Read-only tools · 35
Unusual tool instructions. 1 tool description contain text aimed at the AI model rather than at you (reaches for local secrets). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age98 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 23d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars31Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
Tools exposed42Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Rebase works

What Rebase MCP server does

Rebase MCP server gives AI agents an operational interface to a Rebase backend project. Its tools cover the project’s TypeScript collection definitions, generated Drizzle schema, live PostgreSQL database, application documents, registered users, roles, storage objects, database branches, and local development server.

Schema and database tools support the full change workflow. Agents can generate Drizzle schema files from collection definitions, inspect an existing database and produce collection definitions, preview the SQL for a proposed collection change, create migration files, and apply pending migrations. A diagnostic tool checks for differences between collection definitions, generated schema, and the live database. The server can also generate a typed JavaScript or TypeScript SDK from the collections.

Data-management tools handle listing, reading, creating, updating, and deleting documents in Rebase collections. Separate user and role tools support account administration, including password resets through the admin API. Storage tools list objects, delete files, and create temporary signed download URLs.

How it works

The tools operate against the Rebase backend and its database rather than providing a separate data model. Collection definitions are the source for generated Drizzle schema and SDK output, while database introspection works in the opposite direction by creating collection definitions from existing tables.

For schema changes, rebase_schema_plan previews the SQL without executing it or writing files. rebase_db_generate creates migration files by comparing the current schema with the previous entity, and rebase_db_migrate applies pending SQL migrations. rebase_db_push offers a direct development update to the database, skipping migration files.

Development-server controls start the Rebase frontend and backend, read recent output, or stop the running process. Starting returns immediately, so logs are read separately. Branch tools create, list, inspect, switch, and delete database branches, or report the active branch when no name is supplied.

Tools and capabilities

  • Generate and introspect Rebase collection schemas.
  • Preview, generate, and apply database changes.
  • Detect drift across collections, Drizzle schema, and PostgreSQL.
  • Generate a typed JavaScript or TypeScript SDK.
  • Create, read, update, delete, filter, sort, and paginate collection documents.
  • Administer users, roles, and password resets.
  • Manage database branches and local branch selection.
  • Start, inspect, and stop the Rebase development server.
  • List and delete storage objects and mint signed download URLs.

Limitations and notes

Database branch operations are marked for administrators. Direct schema push refuses changes that would destroy data; the intended workflow is to inspect the plan first and have a human run the CLI command with --allow-destructive when appropriate.

Rows returned by document tools are application data written by users and should be treated as untrusted data, not instructions. Signed download URLs are bearer capabilities: possession of a returned URL can provide access after the tool call until it expires. The development database schema-plan endpoint changes nothing and writes no files.

Written by AllMCPs with AI assistance from the project’s README and listing data. How we build listings

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Rebase

Rebase is an MCP server that connects AI agents to a Rebase backend project and its PostgreSQL database. Its main tools manage collection schemas, migrations, documents, users, roles, storage, database branches, SDK generation, and the Rebase development server, including schema planning and drift detection.

Use `rebase_schema_plan` to preview the SQL without applying it or writing files. The result identifies each statement and marks changes that would destroy data, making it the review step before proposing a schema update.

No, `rebase_db_push` refuses changes that destroy data. Use `rebase_schema_plan` first, then have a human run `rebase db push --allow-destructive` when that operation is intentional.

Use `list_documents`, `get_document`, `create_document`, `update_document`, and `delete_document`. Listing supports optional filtering, sorting, and pagination, while returned rows should be treated as untrusted application data.

Use `rebase_dev_start` to start the frontend and backend, then `rebase_dev_logs` to read recent output. The start tool returns immediately; use `rebase_dev_stop` when the running development server should be stopped.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRebase AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rebase?style=directory)](https://allmcps.com/mcp/rebase)
HTML Embed
<a href="https://allmcps.com/mcp/rebase"><img src="https://allmcps.com/api/badge/rebase?style=directory" alt="Rebase on AllMCPs" /></a>