@rushdb/mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @rushdb/mcp-server@3.4.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 1 returned a result.
getSchema | No usable answer tool reported an error: It seems like you haven't configured your RushDB credentials. Would you like me to open the RushDB dashboard for you so you can sign up |
findLabels | No usable answer tool reported an error: It seems like you haven't configured your RushDB credentials. Would you like me to open the RushDB dashboard for you so you can sign up |
findRelationships | No usable answer tool reported an error: It seems like you haven't configured your RushDB credentials. Would you like me to open the RushDB dashboard for you so you can sign up |
listRelationshipPatterns | No usable answer tool reported an error: It seems like you haven't configured your RushDB credentials. Would you like me to open the RushDB dashboard for you so you can sign up |
getQueryBuilderPrompt | Returned a result under 0.1 s · 9,721 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
2 tools with commands in capitals or very long text
- Gives the agent orders in
findLabels:or filter available record types (labels) and their counts. IMPORTANT: getSchemaMarkdown already returns ALL label names in STEP 0 — do NOT call findLabels as a substitu
- Gives the agent orders in
findRecords:s request (count/total/sum/avg/breakdown/top N by metric) → MUST include select + groupBy. NEVER fetch raw records to count/sum manually. RESPONSE: { data:[...recor
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
getSchemaMarkdown labels, force
STEP 0 — call this ONCE at the start of every conversation before constructing any query. Returns the complete graph schema as compact Markdown: all labels with record counts, all properties per label with their type and value ranges (min/max for numbers/datetimes, sample values for strings/booleans; array properties render as type[]), and all cross-label relationships with direction and edge property summaries. The Properties table includes a "Semantic Search" column: properties with an embedding index show `sourceType similarityFunction dimensionsd [status]` (e.g. `managed cosine 1536d [ready]`); others show `—`. A non-`—` value means the property is queryable with aiSemanticSearch. This single call replaces the need for separate findLabels + findProperties + findRelationships discovery calls. Use the result to determine exact label names (case-sensitive), field names, field types, and relationship patterns before building any findRecords query. Optionally pass `labels` array to narrow the output to specific labels. Pass `force: true` to bypass the 1-hour schema cache and force a fresh recalculation.
getSchema labels, force
Returns the same graph schema as getSchemaMarkdown but as structured JSON. Each item has: label (string), count (number), properties (array with id, name, type, optional isArray, recordsCount (number of records that carry this property), min/max for numbers/datetimes, values[] for strings/booleans, and an optional vectorIndexes array), and relationships (array with label, type, direction: in|out, count, and optional edge properties). vectorIndexes is non-empty when one or more embedding indexes exist for that property; each entry has: id, sourceType (managed|external), similarityFunction (cosine|euclidean), dimensions (number), status (pending|indexing|ready|error), modelKey. A non-empty vectorIndexes means the property is queryable with aiSemanticSearch. Use this when you need property `id` values to pass to propertyValues for deeper drill-down. For initial schema orientation, getSchemaMarkdown uses fewer tokens. Pass `force: true` to bypass the 1-hour schema cache and force a fresh recalculation.
findLabels where, limit, skip, orderBy
List or filter available record types (labels) and their counts. IMPORTANT: getSchemaMarkdown already returns ALL label names in STEP 0 — do NOT call findLabels as a substitute for it. Only call findLabels when you need label counts after applying record-scoped predicates, or getSchemaMarkdown was not called yet. Call with no arguments to list all labels. `where` is applied to Records, not label metadata; use getSchemaMarkdown to search label names. Returns objects with name (case-sensitive — use exact casing in all subsequent calls) and count (number of matching records). Pick the best matching label by: exact match > starts-with > substring > semantic similarity, preferring higher count on ties. State your label assumption briefly ("using DEAL for 'deals'") and proceed without asking.createRecord label, data, transactionId, options
Create a new record. Use the exact label casing returned by findLabels. Set mergeStrategy + mergeBy in options to enable upsert semantics (merge existing vs. replace).
updateRecord recordId, label, data, transactionId
Partially update a record — only fields present in data are changed; all other existing fields are preserved. Use setRecord instead if you want to replace all fields. Requires recordId: retrieve it first with findRecords or getRecord if not already known.
48 more tools
deleteRecord recordId, transactionId
Delete a single record by ID. Irreversible. Always confirm with the user before calling. Use findRecords to preview the record first.
findRecords labels, where, limit, skip, orderBy, select, groupBy
Primary read/query/list/search tool for records. Use findRecords to find records, search records, list records, retrieve matching records, filter records, or answer questions from data. Use this instead of exportRecords unless the user explicitly asks for CSV/export/download. Search records with a structured SearchQuery. BEFORE building any query with dates, metrics, groupBy, relationship traversal, or vector search — call getSearchQuerySpec to load the complete syntax reference. INTENT: metrics/analytics request (count/total/sum/avg/breakdown/top N by metric) → MUST include select + groupBy. NEVER fetch raw records to count/sum manually. RESPONSE: { data:[...records], total:N } — for simple "how many" read total directly; no count select needed. HARD RULES: (1) NEVER set limit when select is present — restricts the record scan and produces mathematically wrong results. Omit limit for all metrics queries. (2) labels contains root records only; put related labels inside where traversal blocks with $alias when referenced. (3) groupBy never accepts alias-only values like "$record"; use "$record.name" or a select key. (4) Ambiguous/incomplete named references should use $contains on a display property confirmed via schema discovery, not exact equality. (5) Related-count rankings keep the requested parent/entity as root; count the related alias and order desc for most/more or asc for least/less/fewer.getRecord recordId
Fetch a single record by its ID. Use when you already have the ID from a previous findRecords or findOneRecord call.
getRecordsByIds recordIds
Fetch multiple records by their IDs in one call. Use after collecting IDs from a findRecords query.
attachRelation sourceId, targetId, targetIds, relationType, direction, properties, transactionId
Create a directed or bidirectional relationship between records. sourceId and targetId/targetIds must already exist — use findRecords to resolve records by name/attribute first.
updateRelation sourceId, targetId, targetIds, relationType, direction, set, unset, types
Change the properties of existing relationships of one type between a record and target records: `set` writes values (null stores an explicit null), `unset` removes properties. Pairs without such a relationship are skipped; `updated` counts the relationships changed. Not available inside a transaction. Use findRelationships first to confirm the relationship type, direction and current properties.
detachRelation sourceId, targetId, targetIds, relationType, direction
Remove the relationships between a record and target records. Without relationType it removes relationships of every type; with direction "bidirectional" it removes them both ways. Not available inside a transaction. Use findRelationships to inspect existing relationships and confirm the correct type/direction before detaching.
findRelationships where, source, target, limit, skip, orderBy
Discover and traverse relationships between records. Use this tool in two scenarios: (1) Multi-hop path discovery — fetch a sample record ID, then call findRelationships with source.where or target.where containing that ID to reveal adjacent labels; repeat to trace the full path before building a nested findRecords where clause. (2) Edge filtering — where applies to relationship type/properties; use source/target for endpoint record predicates. Does NOT support select or groupBy — use findRecords for metrics/analytics across related labels.
listRelationshipPatterns
List inferred relationship patterns for the current project. Returns suggestions and their lifecycle status, current schema relationship summaries, and the latest analysis status. Use this before approving, ignoring, or deleting a relationship pattern.
analyzeRelationshipPatterns
Queue schema analysis to generate relationship pattern suggestions for the current project. This may invoke the configured LLM. Poll listRelationshipPatterns to inspect completion status and suggestions.
approveRelationshipPattern id
Approve and apply a suggested relationship pattern. Call listRelationshipPatterns first so the user can review the inferred source, target, direction, type, mode, and confidence.
ignoreRelationshipPattern id
Ignore a suggested relationship pattern without applying it. Call listRelationshipPatterns first so the user can review the inferred pattern.
deleteRelationshipPattern id, deleteExisting
Delete a saved relationship pattern. Irreversible. Confirm with the user before calling. When deleteExisting is true, relationships previously materialized by this pattern are also removed.
bulkCreateRecords label, data, transactionId, options
Insert multiple records of the same label in one call. Set mergeStrategy ("append" to keep existing unspecified fields, "rewrite" to replace) and mergeBy (fields to match on) in options to enable upsert semantics. Use the exact label casing returned by findLabels.bulkDeleteRecords labels, where, transactionId
Delete all records matching a query. IRREVERSIBLE and potentially high-impact. REQUIRED: always call findRecords with the same labels+where first to show the user a preview, then ask for explicit confirmation before calling this tool.
exportRecords labels, where, limit, orderBy
Export matching records as a CSV file only when the user explicitly asks to export/download CSV. For normal reading, answering, listing, searching, or inspecting records, use findRecords instead. Accepts the same labels/where/orderBy filters as findRecords. Call findProperties first to know available field names if constructing a where filter.
helpAddToClient
Help the user add the RushDB MCP server to their MCP client
getQueryBuilderPrompt
Return the RushDB system prompt. Use this if your MCP client does not support the Prompts API.
getSearchQuerySpec
Returns the complete RushDB SearchQuery specification as a focused reference document. Covers: all WHERE operators (string/number/boolean/datetime component objects/vector/$exists/$type), relationship traversal syntax ($alias/$relation with variable-length hops/$cycle ring detection/$id), logical grouping ($and/$or/$not/$nor/$xor), all select functions ($sum/$avg/$min/$max/$count/$collect/$timeBucket), both groupBy modes (dimensional + self-group), late-ordering rules, root-label vs related-label traversal rules, COLLECT nesting, limit rules by query mode, multi-hop path discovery, enum normalization, validation checklist, and annotated query examples. CALL THIS before building any findRecords query that involves dates, metrics, groupBy, relationship traversal, or vector search. Do not guess operator syntax — use this spec as the source of truth.
setRecord recordId, label, data, transactionId
Replace ALL fields of a record with the provided data object — any existing fields not in data are deleted. Use updateRecord instead for partial/merge updates that preserve unspecified fields.
findOneRecord labels, where
Return the first record matching the query — useful for entity resolution probes. Call with where: { <nameField>: { $contains: "..." } } and a small limit to resolve a named entity to its ID before using it in a relationship filter. Prefer this over findRecords when you need exactly one representative match rather than a full list.findUniqRecord labels, where
Return the single record that uniquely matches the query — throws if zero or more than one record matches. Use for unique-key lookups (email, code, slug) where exactly one result is expected. Use findOneRecord instead when you only want the first match and duplicates are acceptable.
deleteRecordById recordId, transactionId
Delete a single record by ID. Irreversible. Always confirm with the user before calling. Use getRecord to preview the record if needed.
propertyValues propertyId, query, match, domainOnMiss, orderBy, limit, skip
Get statistics or distinct values for a specific property, identified by the `id` field returned from findProperties. What this tool returns depends on the property type:
• number / datetime → returns { min, max } — use this to answer range, min/max, or spread questions for numeric or date fields. No findRecords aggregation needed.
• string / boolean → returns a list of all distinct values — use this to canonicalize filter values before querying.
Workflow for range/min/max questions: (1) findLabels, (2) findProperties to find the field and get its id and type, (3) call this tool with that id if type is number or datetime.searchValues text, match, labels, limit, minSimilarity
Find where a value from the question is stored: searches the exact value dictionaries of every property at once and returns { matches: [{ label, property, value, count }], total }. Use it before filtering on a name, code, or phrase the user typed, instead of guessing the field or spelling. match: contains (default), prefix, exact, or similar (near spellings, for typos and punctuation: "spiderman" finds "Spider-Man"). No match means no stored value contains the text: check the spelling, try a shorter word, or read a field's values with propertyValues.getSchemaSummary labels, fewValues
Every label with its properties in one live read (never cached): per property its type, record count, exact distinct count, min/max for numbers and dates, and the full value list when it holds few (fewValues, default 10); per label its relationships. Use it to learn how values are coded (e.g. KCT holds "-" and "+") without one call per field.
resolveNames text, limit
Find the real label or property behind a name you are unsure of (case, separators and plural endings ignored, then ranked by spelling): "patients" → Patient, "patients.birthdate" → Patient.Birthday. Call it instead of guessing when a label or field name is not in the schema. Returns [{ label, property?, score }].getJoinCandidates labels, minConfidence
Which properties reference records of another label (or the same one), found from property names and exact value containment, with evidence (matched values and records, coverage). RushDB Cloud only. Use it to learn how labels connect when the data has no relationships yet, e.g. before joining in a query. Returns [{ source, target, reasons, relationshipType, confidence, evidence, rationale }].findProperties where, limit, skip, orderBy
Discover the field names, types, and IDs available on a record label. Always call this before using field names in any query — never guess or invent field names. Filter by label using labels: ["LABEL_NAME"]. `where` is applied to Records, not property metadata. Each returned property object has: id (string), name (string), type (string | number | boolean | datetime), recordsCount (number of records that carry this property). Use the `name` field as the field name in where/orderBy/groupBy clauses. Use the `id` field as the `propertyId` argument to propertyValues. After calling this tool, decide the next step based on the field type: number or datetime → call propertyValues(propertyId) to get { min, max } for range questions, OR use findRecords with select: { min: ..., max: ... }; string or boolean → call propertyValues(propertyId) to get distinct values before filtering.findPropertyById propertyId
Fetch the metadata (name, type, label, recordsCount) of a single property by its ID. Use when you already have a propertyId and need to re-confirm its type or cardinality before calling propertyValues.
deleteProperty propertyId
Permanently delete a property and all its values from every record that has it. Irreversible. Confirm with the user before calling.
findEmbeddingIndexes
List all embedding index policies configured for the current project. Each index entry contains: id, label, propertyName, modelKey, dimensions, enabled, status (pending|indexing|ready|error), createdAt, updatedAt. Call this before creating a new index to check if one already exists for the same label+propertyName.
createEmbeddingIndex name, label, propertyName, sourceType, similarityFunction, dimensions
Create a new embedding index policy for a string property. For managed indexes (default), RushDB asynchronously embeds every existing value and keeps new values embedded on write. For external indexes (sourceType: "external"), the client supplies vectors via upsertEmbeddingVectors. Once the index status becomes "ready" (check with getEmbeddingIndexStats), use vectorSearch to query.
upsertEmbeddingVectors indexId, items
Write pre-computed embedding vectors to an external vector index for a set of records. Only valid for indexes with sourceType "external". Each vector must contain exactly as many dimensions as the index was created with. After upserting, call getEmbeddingIndexStats to check if all records are indexed (status becomes "ready").
deleteEmbeddingIndex indexId
Delete an embedding index policy by its ID and strip all stored embedding vectors for that index. Irreversible. Confirm with the user before calling. Use findEmbeddingIndexes to get the indexId.
getEmbeddingIndexStats indexId
Return indexing statistics for an embedding index: totalRecords and indexedRecords. Use this to monitor backfill progress after creating an index — when indexedRecords === totalRecords the index is fully ready.
vectorSearch index, propertyName, query, queryVector, labels, sourceType, similarityFunction, dimensions, where, mode, ef, scoreThreshold, weight, prefetchLimit, fusion, rrfK, text, limit, skip
Perform direct vector similarity search over records whose `propertyName` has been indexed with createEmbeddingIndex. For managed indexes: provide a free-text `query` — RushDB embeds it and returns the most similar records ranked by similarity (__score). For external indexes: provide a `queryVector` (pre-computed number[]) instead of query text. A `where` filter narrows candidates before ranking. Requires an embedding index in "ready" status for the given label+propertyName.
listTextIndexes
List the project's keyword (BM25) text indexes: name, label, property ("*" = every string of the record), consistency and status.createTextIndex label, property, name, consistency
Declare a keyword (BM25) text index over one property of a label, or every string of it (property "*"). It is built online; once its status is "ready" (listTextIndexes), search it with textSearch or as the `text` leg of vectorSearch.
deleteTextIndex name
Drop a text index by name. Irreversible. Confirm with the user before calling.
textSearch query, index, property, labels, where, allTerms, phrase, limit, skip
Keyword (BM25) search over a text index: records matching `query`, best first (__score), among those `labels` and `where` select. `total` counts every match. Query syntax: words match any (or all with allTerms), "quoted phrases", -excluded, +required.
semanticSearch propertyName, query, queryVector, labels, sourceType, similarityFunction, dimensions, where, mode, ef, scoreThreshold, limit, skip
Deprecated alias for vectorSearch. Performs direct vector similarity search over records whose `propertyName` has been indexed with createEmbeddingIndex. Prefer vectorSearch for new integrations. For natural-language schema-aware querying, use smartSearch.
listConnections
List the project's connections to SaaS tools (CRM, billing, support, issue tracking, docs, spreadsheets), custom APIs and webhooks. Each has its status (ready, paused, needs_reauth), mode and schedule, lastSuccessAt, lastError, the running sync (activeRunId) and per-stream label, record count and lastSyncedAt. Use it to tell where a label's records come from and how fresh they are before answering questions about recent data.
getConnection id
One connection by id (from listConnections): status, schedule (nextRunAt), last run and success, last error, and per-stream record counts and lastSyncedAt. Credentials are never returned.
syncConnection id, streams, full
Start a sync of a connection now, to refresh its data: every enabled stream, or the streams named. Returns the queued import run; follow it with getImport until its status is completed, partial, failed or cancelled. Only when the user asks for fresh data or the connection's lastSuccessAt is too old for the question; a sync writes to the project. full: true re-reads everything from the start (slow; only when asked or when incremental data looks wrong). If a sync is already queued or running, that run is returned instead of a new one. Push (webhook) connections cannot be synced.
listImports kind, connectionId, limit, skip
List import runs, newest first: background file imports (kind "file") and connection syncs (kind "sync"), with status, records written and deleted, links created, errors and timing. Filter by kind or connectionId to see the sync history of one connection.
getImport id
One import run by id (a file import or a connection sync, e.g. the run syncConnection returned): status (queued, running, paused_billing, completed, partial, failed, cancelled), progress per file or stream, error sample, and once finished a summary (labels written, relationship suggestions pending review).
smartSearch prompt, limit, skip
Convert a natural-language question into one read-only SQL statement over the project schema, run it, and return the results plus the statement, a short title for it and any warnings. Rows that select a record come back as records; aggregates such as counts and totals come back as plain rows. Use this for user-facing questions such as "Who are piloting Falcon?" or "How many orders per city?". For direct vector similarity over an embedding index, use vectorSearch instead.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/rush-db/mcp-server |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-o0cu04R4XNsyXp6CJVRT2hrtD2QCIchVdmAQpyEbOlKIVChH/n/u/gMs8gD0CuZe2+9XLKUBSM/H6ajKqghmkw== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 3.4.1 | 2026-11-16 | Starts with no setup | 53 |
| 3.4.0 | 2026-11-12 | Starts with no setup | 53 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40rushdb/mcp-server)
New version out? Ask for a fresh report.