Elasticsearch MCP Server vs Rebase

A side-by-side look at the Elasticsearch 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.

Elasticsearch MCP Server logoElasticsearch MCP ServerDatabases · Local subprocess (stdio)MCP Server implementation that provides Elasticsearch interaction65GreatAuth: api key requiredRebase logoRebaseDatabases · Local subprocess (stdio)Schema, database, document, user and dev-server tools for a Rebase backend project.65GreatAuth: not declared

Verdict: choose Elasticsearch 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?

Elasticsearch MCP Server logoChoose Elasticsearch MCP Server when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You want tools like list_indices, get_index, create_index.
Explore Elasticsearch MCP Server

Rebase logoChoose 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.
Explore Rebase

Feature & specification comparison

Rows where the two servers differ are marked.

SpecElasticsearch MCP Server logoElasticsearch MCP ServerRebase logoRebase
CategoryDatabasesDatabases
Quality signal65/100 · Great65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars31323
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools2042

Tools & capabilities

Elasticsearch MCP Server tools 20

  • list_indicesList all indices.
  • get_indexReturns information (mappings, settings, aliases) about one or more indices.
  • create_indexCreate a new index.
  • delete_indexDelete an index.
  • search_documentsSearch for documents.
  • index_documentCreates or updates a document in the index.
  • get_documentGet a document by ID.
  • delete_documentDelete a document by ID.
  • delete_by_queryDeletes documents matching the provided query.
  • get_cluster_healthReturns basic information about the health of the cluster.
  • get_cluster_statsReturns high-level overview of cluster statistics.
  • list_aliasesList all aliases.
  • +8 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.

Elasticsearch MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cr7258-elasticsearch-mcp-server": {
      "command": "uvx",
      "args": [
        "elasticsearch-mcp-server"
      ]
    }
  }
}

Rebase

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "rebase": {
      "command": "npx",
      "args": [
        "-y",
        "@rebasepro/mcp"
      ]
    }
  }
}

Frequently asked questions

Elasticsearch MCP Server is categorized under Databases and uses a local stdio subprocess. Rebase belongs to Databases and uses a local stdio subprocess. Pick Elasticsearch 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.

Elasticsearch MCP Server is listed as free. Auth: api key required. 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 cr7258-elasticsearch-mcp-server and rebase as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Elasticsearch MCP Server has a quality signal of 65/100 (Great) with 3 views, 0 installs and 313 GitHub stars. Rebase has 65/100 (Great) with 1 views, 0 installs and 23 GitHub stars.