ZeroDB MCP Server vs Rebase
A side-by-side look at the ZeroDB MCP Server and Rebase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ZeroDB MCP Server for databases work as a local process; choose Rebase for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ZeroDB MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ZERODB_API_URL, ZERODB_PROJECT_ID, ZERODB_API_KEY. - You want tools like
zerodb_generate_embeddings, zerodb_embed_and_store, zerodb_semantic_search.
Choose Rebase when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
rebase_schema_generate, rebase_db_push, rebase_schema_introspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 63/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ZERODB_API_URLZERODB_PROJECT_IDZERODB_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 23 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 85 | 42 |
| Full listing | View ZeroDB MCP Server | View Rebase |
Tools & capabilities
ZeroDB MCP Server tools 85
zerodb_generate_embeddingsGenerate embeddings using specified model (384/768/1024 dimensions). Supports BAAI/bge-small-en-v1.5 (384-dim, default), BAAI/bge-base-en-v1.5 (768-dim), BAAI/bge-large-en-v1.5 (1024-dim). Use when you need raw embedding vectors without storing them. Does not persist data — for embed + store in one step, use zerodb_embed_and_store instead.zerodb_embed_and_storeGenerate embeddings and store in ZeroDB in one step. Auto-detects dimension based on model and routes to correct storage. Use when you want to embed text and persist the vectors in a single call. Combines zerodb_generate_embeddings + zerodb_upsert_vector.zerodb_semantic_searchSemantic search using text query (auto-embeds query text). Searches vectors in the same dimension as the model used. Use when searching vectors using a text query (auto-embeds the text). Unlike zerodb_search_vectors which requires a raw vector, this accepts plain text. Unlike zerodb_search_memory which searches agent conversation memory, this searches the general vector store.zerodb_store_memoryStore agent memory in ZeroDB for persistent context. Use when the agent needs to persist conversation turns, decisions, or observations for later recall. Stores with role, session, and agent metadata for filtered retrieval.zerodb_search_memorySearch agent memory using semantic similarity. Use when searching agent conversation memory by natural language. Unlike zerodb_search_vectors which requires a raw vector, and zerodb_semantic_search which searches the general vector store, this searches agent-specific memory entries filtered by session/agent/role.zerodb_get_contextGet agent context window for current session. Use when the agent needs to retrieve its recent conversation context within token limits. Returns the most recent memories for a session, bounded by max_tokens.zerodb_upsert_vectorStore or update a vector embedding with metadata. Supports 384, 768, 1024, or 1536 dimensions. Dimension is auto-detected and validated. Use when you have a pre-computed embedding vector to store or update. For embedding text and storing in one step, use zerodb_embed_and_store instead.zerodb_batch_upsert_vectorsBatch upsert multiple vectors for efficiency. Use when storing many vectors at once to reduce API round-trips. Accepts an array of vector objects and processes them in a single request.zerodb_search_vectorsSearch vectors using semantic similarity. Supports 384, 768, 1024, or 1536 dimension query vectors. Auto-detects dimension. Use when searching raw vector embeddings by similarity with a query vector. Unlike zerodb_semantic_search which accepts text (auto-embeds), this requires a pre-computed vector. Unlike zerodb_search_memory which searches agent memory, this searches the general vector store.zerodb_delete_vectorDelete a specific vector by ID. Use when removing a single vector embedding from the store. WARNING: This operation is irreversible.zerodb_get_vectorRetrieve a specific vector by ID. Use when you need to inspect a particular vector's metadata or embedding values. Optionally includes the full embedding array.zerodb_list_vectorsList vectors in a project/namespace with pagination. Use when the agent needs to browse or enumerate stored vectors, or answer "what vectors exist?". Supports filtering by namespace and metadata.- +73 more on the listing page
Rebase tools 42
rebase_schema_generateGenerate Drizzle schema from Rebase TypeScript collection definitions. Run this after adding or modifying collection files.rebase_db_pushApply the current Drizzle schema directly to the database (development shortcut, skips migration files). Refuses changes that destroy data — use rebase_schema_plan first, then ask the human to run `rebase db push --allow-destructive`.rebase_schema_introspectIntrospect the live database and generate Rebase collection definitions from existing tables.rebase_db_generateGenerate SQL migration files from schema changes (compares current Drizzle schema against the last entity).rebase_db_migrateRun all pending SQL migrations against the database.rebase_generate_sdkGenerate a fully-typed JavaScript/TypeScript SDK from collection definitions.rebase_doctorDetect schema drift between collection definitions, generated Drizzle schema, and the live PostgreSQL database.rebase_db_branch_createCreate a new database branch (Admins only).rebase_db_branch_listList all database branches (Admins only).rebase_db_branch_deleteDelete an existing database branch (Admins only).rebase_db_branch_infoShow information and status for a database branch (Admins only).rebase_db_branch_switchPoint this checkout at a database branch, or back at the main database (Admins only). With no name, reports which branch is active. Writes a local pointer, never `.env`.- +30 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ZeroDB MCP Server
{
"mcpServers": {
"ainative-zerodb-mcp-server": {
"command": "npx",
"args": [
"ainative-zerodb-mcp-server"
],
"env": {
"ZERODB_API_URL": "YOUR_ZERODB_API_URL_HERE",
"ZERODB_PROJECT_ID": "YOUR_ZERODB_PROJECT_ID_HERE",
"ZERODB_API_KEY": "YOUR_ZERODB_API_KEY_HERE"
}
}
}
}
Rebase
{
"mcpServers": {
"rebase": {
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
Frequently asked questions
ZeroDB MCP Server is categorized under Databases and uses a local stdio subprocess. Rebase belongs to Databases and uses a local stdio subprocess. Pick ZeroDB MCP Server for databases work and Rebase for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ZeroDB MCP Server has no declared pricing — check the project's own site. Rebase has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ainative-zerodb-mcp-server and rebase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ZeroDB MCP Server has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Rebase has 65/100 (Great) with 1 views, 0 installs and 23 GitHub stars.