RushDB
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUSHDB_API_KEY | Yes | RushDB API key | |
| RUSHDB_API_URL | No | Base API URL (defaults to https://api.rushdb.com/api/v1) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| FindLabelsB | Find / filter record labels (supports where, limit, skip, orderBy). Superset of GetLabels. |
| CreateRecordC | Create a new record in the database |
| UpdateRecordC | Update an existing record (partial update) |
| DeleteRecordC | Delete a record from the database (alias of DeleteRecordById) |
| FindRecordsC | Find records in the database using a search query |
| GetRecordB | Get a specific record by ID |
| GetRecordsByIdsC | Get multiple records by their IDs |
| AttachRelationC | Create a relationship between records (single or multiple targets) |
| DetachRelationB | Remove a relationship between records (single or multiple targets) |
| FindRelationshipsC | Find relationships in the database |
| BulkCreateRecordsC | Create multiple records in a single operation |
| BulkDeleteRecordsC | Delete multiple records matching a query |
| ExportRecordsC | Export records to CSV format |
| OpenBrowserC | Open a web browser to a specific URL |
| HelpAddToClientA | Help the user add the RushDB MCP server to their MCP client |
| GetQueryBuilderPromptA | Return the RushDB Query Builder system prompt. Use this if your MCP client does not support Prompts API. |
| SetRecordC | Replace all fields of a record with provided values |
| FindOneRecordC | Find a single record that matches the given search criteria |
| FindUniqRecordC | Find a unique record that matches the given search criteria |
| DeleteRecordByIdC | Delete a record by its ID |
| PropertyValuesC | Get values for a specific property |
| FindPropertiesC | Find properties in the database using a search query |
| FindPropertyByIdC | Find a specific property by ID |
| DeletePropertyC | Delete a property from the database |
| TransactionBeginB | Begin a new database transaction |
| TransactionCommitC | Commit a database transaction |
| TransactionRollbackC | Rollback a database transaction |
| TransactionGetC | Get information about a transaction |
| GetSettingsB | Get the current database settings and configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| rushdb.queryBuilder | RushDB Query Builder system prompt: guides the model to discover labels/properties first and construct validated SearchQuery objects before calling find-related tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Most tools have distinct purposes with clear boundaries, such as CreateRecord vs. UpdateRecord vs. DeleteRecord. However, there is some overlap between DeleteRecord and DeleteRecordById (described as aliases), and FindOneRecord vs. FindUniqRecord could be confusing without careful reading of descriptions, though the latter emphasizes uniqueness.
Tool names follow a consistent verb_noun pattern (e.g., CreateRecord, DeleteRecord, FindRecords) with clear action-object pairs. Minor deviations include GetQueryBuilderPrompt and HelpAddToClient, which are more descriptive but still maintain readability without disrupting the overall pattern.
With 29 tools, the count feels heavy for a database server, potentially overwhelming for agents. While it covers many operations, it could be streamlined by merging redundant tools like DeleteRecord and DeleteRecordById, or consolidating some find operations to reduce complexity.
The tool set provides comprehensive coverage for database operations, including CRUD (CreateRecord, GetRecord, UpdateRecord, DeleteRecord), bulk operations, relationships (AttachRelation, DetachRelation), transactions, and utilities like export and settings. No obvious gaps exist for core database workflows.