StackQL MCP Server vs Rebase
A side-by-side look at the StackQL 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 StackQL 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 StackQL MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
describe_method, list_methods, list_providers.
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 | 71/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,067 | 23 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 15 | 42 |
| Full listing | View StackQL MCP Server | View Rebase |
Tools & capabilities
StackQL MCP Server tools 15
describe_methodFull I/O contract for one method: every input with its param_type (input_required params become exact-match WHERE predicates; input_optional ones may be added) and every output field, which are the columns a SELECT or RETURNING can reference. Call it after list_methods and before the first query against a method; there is no resource-level equivalent because each method returns its own shape. Requires provider, service, resource, method.list_methodsAccess methods (HTTP operations) for a resource with their SQL verb and required params. Pick the method whose verb matches the intent and whose required params you can supply, then describe_method it. Call when composing SQL from scratch against an unfamiliar resource; not needed when executing a vetted query library template. Requires provider, service, resource.list_providersAvailable cloud/SaaS providers (top of the hierarchy). No inputs.list_registryProviders (and their versions) available in the configured registry. Distinct from list_providers, which lists only providers already pulled. Optional provider arg lists versions for that provider.list_resourcesResources under a provider.service. Requires provider and service.list_servicesServices under a provider. Requires provider.pull_providerInstall a single provider from the registry into the local approot cache. Requires provider; version is optional (latest published is pulled when empty). Writes only local cache state; no cloud control/data plane effect.query_library_getRetrieve a query library entry by id. Without params: returns the raw template, param declarations and notes (adapt from it when no exact match exists). With params: the server validates values and returns rendered SQL plus which tool to execute it with (run_select_query or run_mutation_query). Read-only, no credentials.query_library_searchSearch the curated StackQL query library by natural-language intent. Returns ranked template ids. Consult before composing SQL from scratch; follow with query_library_get, which validates params and surfaces any the index omits. Read-only, no credentials.reload_credentialsLive-reload provider credentials: re-sources the server's configured env file into the process environment, invalidates cached auth contexts, and reports resolution status for every installed provider (optional provider arg filters the report; changed field flags values that differ from before). Never returns secret values. Credentials resolve automatically at query time - never call this at session start or before queries. Call only after a query fails with a credential resolution error (fix the env file first, then reload, then retry) or when the user says credentials have been rotated or changed. If the report shows changed: false after a failure, the file was not updated - ask the user rather than retrying.run_lifecycle_operationExecute a stackql EXEC lifecycle operation (eg EXEC aws.ec2.instances.start_instances ...). Real cloud side effects. Discover available operations and required params via list_methods and describe_method. Returns {messages, timestamp}. Gated by server mode.run_mutation_queryExecute INSERT/UPDATE/REPLACE/DELETE against the provider. Real side effects. Returns {messages, timestamp}. Gated by server mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.- +3 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.
StackQL MCP Server
{
"mcpServers": {
"stackql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}
Rebase
{
"mcpServers": {
"rebase": {
"command": "npx",
"args": [
"-y",
"@rebasepro/mcp"
]
}
}
}
Frequently asked questions
StackQL MCP Server is categorized under Databases and uses a local stdio subprocess. Rebase belongs to Databases and uses a local stdio subprocess. Pick StackQL 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.
StackQL MCP Server is listed as free. 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 stackql-mcp-server and rebase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, StackQL MCP Server has a quality signal of 71/100 (Great) with 5 views, 0 installs and 1,067 GitHub stars. Rebase has 65/100 (Great) with 1 views, 0 installs and 23 GitHub stars.