Chroma’s official MCP server: vector search and collection management for RAG workflows.
Docbase is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MongoDB tools: query, aggregate, index, and administer collections and databases.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user cloudcorprecords-docbase-mcp '--' npx -y @reneturcios/docbase mcp
# 2 — ask your agent for something these tools do
# connect, list-databases, list-collections and 19 more
Docbase costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Docbase as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user cloudcorprecords-docbase-mcp '--' npx -y @reneturcios/docbase mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Connect to a MongoDB instance
| Parameter | Type | Required | Notes |
|---|---|---|---|
| connectionString | string | no | MongoDB connection string (mongodb:// or mongodb+srv://) to connect with; overrides the configured connection for this call. |
List all databases in the connected MongoDB instance
No parameter schema on file.
List collections in a MongoDB database
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database whose collections to list. |
Describe the schema for a collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose schema to describe. |
List indexes for a collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose indexes to list. |
Get the storage size of a collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose storage size to report. |
Run a find query against a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to query. |
| filter | object | no | MongoDB query filter document matching the documents to return. |
| projection | object | no | Projection document controlling which fields are returned in each document. |
| limit | number | no | Maximum number of documents to return; must be positive. |
| sort | object | no | Sort document mapping each field to its sort direction (1 for ascending, -1 for descending). |
Run an aggregation pipeline against a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to run the aggregation pipeline against. |
| pipeline | array | yes | Aggregation pipeline stages, each an object such as a $match or $group stage, applied in order. |
Count documents in a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose documents to count. |
| query | object | no | Query filter document selecting the documents to count. |
Insert documents into a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to insert the documents into. |
| documents | array | yes | Documents to insert; a non-empty array of objects. |
Update documents in a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose documents to update. |
| filter | object | yes | Filter document selecting the documents to update. |
| update | object | yes | Update document to apply to the matching documents, for example using update operators such as $set. |
Delete documents from a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection whose documents to delete. |
| filter | object | yes | Filter document selecting the documents to delete; all matching documents are deleted. |
Create a new collection in a MongoDB database
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database in which to create the collection. |
| collection | string | yes | Name of the new collection to create. |
Drop a collection from a MongoDB database
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to drop. |
Drop a MongoDB database
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database to drop. |
Rename a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Current name of the collection to rename. |
| newName | string | yes | New name for the collection, within the same database. |
Create an index on a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to create the index on. |
| keys | object | yes | Index keys document mapping each field to its index direction or type (for example 1, -1, or "text"); must name at least one field. |
Drop an index from a MongoDB collection
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to drop the index from. |
| indexName | string | yes | Name of the index to drop from the collection. |
Get the execution plan for a MongoDB query
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection the explained operation runs against. |
| method | array | no | Array naming the operation method to explain; the first entry is used and find is used when this is omitted. |
| methodArgs | object | no | Arguments document for the explained method, merged into the operation being explained. |
Export a MongoDB collection to a file
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database containing the collection. |
| collection | string | yes | Name of the collection to export. |
| exportTitle | string | no | Title for the export; the collection name is used when this is omitted. |
| filter | object | no | Filter document selecting the documents to export. |
Get statistics for a MongoDB database
| Parameter | Type | Required | Notes |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database whose statistics to return. |
Retrieve MongoDB log entries
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Maximum number of log lines to return; must be positive. |
| type | string | no | Log type or component to retrieve; global is used when this is omitted. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Docbase or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| connect | no tags | |
| list-databases | no tags | |
| list-collections | no tags | |
| collection-schema | no tags | |
| collection-indexes | no tags | |
| collection-storage-size | no tags | |
| find | no tags | |
| aggregate | no tags | |
| count | no tags | |
| insert-many | no tags | |
| update-many | no tags | |
| delete-many | no tags | |
| create-collection | no tags | |
| drop-collection | no tags | |
| drop-database | no tags | |
| rename-collection | no tags | |
| create-index | no tags | |
| drop-index | no tags | |
| explain | no tags | |
| export | no tags | |
| db-stats | no tags | |
| mongodb-logs | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Docbase can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.