io.github.mongodb-js/mongodb-mcp-server
OCI · DOCKER.IO/MONGODB/MONGODB-MCP-SERVER · 2 COMPONENTS
MongoDB Model Context Protocol Server
Available components
Last scanned (11 hours ago)
Scores higher than 60% of OCI servers
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3946 tokens (~136/item across 29 items; 27 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (89% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 4 Nov 26 0
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 3.2.1 → 3.2.2 functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/docker.io/mongodb/mongodb-mcp-server@3.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 11 ungraded findings
From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-6j4f-fj2g-mc7p | CVE-2026-102276 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-q2hr-2g5m-vwhr | CVE-2026-102277 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-qhr7-859c-m2p7 | CVE-2026-102278 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-2vr4-cq9g-pvrc | CVE-2026-101910 | medium | yes | |
| GHSA-h3mg-xc3c-68pw | CVE-2026-101911 | medium | yes | |
| GHSA-j6r3-76f7-8jcv | CVE-2026-101912 | medium | yes | |
| GHSA-rpw4-54j3-4h4q | CVE-2026-101913 | medium | yes | |
| GHSA-rxp7-6hxx-x8q5 | CVE-2026-111997 | medium | yes | |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aggregate ~1,365
Run an aggregation against a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| pipeline | array | yes | An array of aggregation stages to execute. If the user has asked for a vector search, `$vectorSearch` **MUST** be the first stage of the pipeline (or the first stage of a `$unionWith` sub-pipeline o… |
| responseBytesLimit | number | – | The maximum number of bytes to return in the response. This value is capped by the server's configured maximum and cannot be exceeded. |
| Name | Type | Req | Description |
|---|---|---|---|
| appliedLimits | array | yes | The limits applied to the aggregation pipeline |
| count | – | yes | The total number of documents returned by the aggregation pipeline |
| documents | array | yes | The documents returned by the aggregation pipeline |
No examples provided.
aggregate-db ~154
Run an aggregation against a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| pipeline | array | yes | An array of aggregation stages to execute. The first stage must be a database-level aggregation stage (one of `$changeStream`, `$currentOp`, `$documents`, `$listLocalSessions`, `$queryStats`). https:… |
| responseBytesLimit | number | – | The maximum number of bytes to return in the response. This value is capped by the server's configured maximum and cannot be exceeded. |
| Name | Type | Req | Description |
|---|---|---|---|
| aggResultsCount | number | – | The total number of documents returned by the aggregation pipeline |
| appliedLimits | array | yes | The limits applied to the aggregation pipeline |
| documents | array | yes | The documents returned by the aggregation pipeline |
No examples provided.
collection-indexes ~60
Describe the indexes for a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| classicIndexes | array | yes | – |
| classicIndexesCount | number | yes | – |
| searchIndexes | array | yes | – |
| searchIndexesCount | number | yes | – |
No examples provided.
collection-schema ~109
Describe the schema for a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| responseBytesLimit | number | – | The maximum number of bytes to return in the response. This value is capped by the server's configured maximum and cannot be exceeded. |
| sampleSize | number | – | Number of documents to sample for schema inference |
| Name | Type | Req | Description |
|---|---|---|---|
| fieldsCount | number | yes | – |
| schema | object | yes | – |
No examples provided.
collection-storage-size ~60
Gets the size of the collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| size | number | yes | – |
| units | string | yes | – |
No examples provided.
connect ~118
Connect to a MongoDB instance and get back a connectionId to pass to the other MongoDB tools. Each call establishes a new, independent connection — multiple connections can be active at the same time.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionName | string | – | Optional short label for the connection (stored slugified with a short suffix, e.g. "staging" becomes staging-<suffix>). Shown in connection listings; helpful for telling multiple connections apart. |
| connectionString | string | yes | MongoDB connection string (in the mongodb:// or mongodb+srv:// format) |
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | – |
No examples provided.
count ~106
Gets the number of documents in a MongoDB collection using db.collection.count() and query as an optional filter parameter
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| query | object | – | A filter/query parameter. Allows users to filter the documents to count. Matches the syntax of the filter argument of db.collection.count(). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | The number of documents in the collection |
No examples provided.
create-collection ~73
Creates a new collection in a database. If the database doesn't exist, it will be created automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| created | boolean | yes | – |
| database | string | yes | – |
No examples provided.
create-index ~111
Create an index for a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| definition | array | yes | The index definition. Use 'classic' for standard indexes, 'vectorSearch' for vector search indexes, and 'search' for Atlas Search (lexical) indexes. |
| name | string | – | The name of the index |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| indexName | string | yes | – |
| indexType | string | yes | – |
No examples provided.
db-stats ~56
Returns statistics that reflect the use state of a single database
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| stats | object | yes | – |
No examples provided.
delete-many ~93
Removes all documents that match the filter from a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| filter | object | – | The query filter, specifying the deletion criteria. Matches the syntax of the filter argument of db.collection.deleteMany() |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| deletedCount | number | yes | – |
No examples provided.
disconnect ~31
Close a MongoDB connection and revoke its connectionId.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connectionId to disconnect. |
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | – |
No examples provided.
drop-collection ~74
Removes a collection or view from the database. The method also removes any indexes associated with the dropped collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| dropped | boolean | yes | – |
No examples provided.
drop-database ~55
Removes the specified database, deleting the associated data files
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | – |
| dropped | boolean | yes | – |
No examples provided.
drop-index ~111
Drop an index for the provided database and collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| indexName | string | yes | The name of the index to be dropped. |
| type | string | yes | The type of index to be deleted. Use 'classic' for standard indexes and 'search' for atlas search and vector search indexes. |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| dropped | boolean | yes | – |
| indexName | string | yes | – |
No examples provided.
explain ~135
Returns statistics describing the execution of the winning plan chosen by the query optimizer for the evaluated method
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| method | array | yes | The method and its arguments to run |
| verbosity | string | – | The verbosity of the explain plan, defaults to queryPlanner. If the user wants to know how fast is a query in execution time, use executionStats. It supports all verbosities as defined in the MongoDB… |
| Name | Type | Req | Description |
|---|---|---|---|
| explainResult | object | yes | – |
| method | string | yes | – |
| verbosity | string | yes | – |
No examples provided.
export ~188
Export a query or aggregation results in the specified EJSON format.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| exportTarget | array | yes | The export target along with its arguments. |
| exportTitle | string | yes | A short description to uniquely identify the export. |
| jsonExportFormat | string | – | The format to be used when exporting collection data as EJSON with default being relaxed. relaxed: A string format that emphasizes readability and interoperability at the expense of type preservation… |
No output schema declared.
No examples provided.
find ~206
Run a find query against a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| filter | object | – | The query filter, matching the syntax of the query argument of db.collection.find() |
| limit | number | – | The maximum number of documents to return |
| projection | object | – | The projection, matching the syntax of the projection argument of db.collection.find() |
| responseBytesLimit | number | – | The maximum number of bytes to return in the response. This value is capped by the server's configured maximum and cannot be exceeded. |
| sort | object | – | A document, describing the sort order, matching the syntax of the sort argument of cursor.sort(). The keys of the object are the fields to sort on, while the values are the sort directions (1 for asc… |
| Name | Type | Req | Description |
|---|---|---|---|
| appliedLimits | array | yes | The limits applied to the find query |
| documents | array | yes | The documents returned by the find query |
| queryResultsCount | number | – | The total number of documents returned by the find query |
No examples provided.
insert-many ~109
Insert an array of documents into a MongoDB collection. If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider inserting them in batches.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| documents | array | yes | The array of documents to insert, matching the syntax of the document argument of db.collection.insertMany(). |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| insertedCount | number | yes | – |
| insertedIds | array | yes | – |
No examples provided.
list-collections ~52
List all collections for a given database
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | yes | – |
| totalCount | number | yes | – |
No examples provided.
list-connections ~30
List the active MongoDB connections and their connectionIds. Use this to find a connectionId established earlier.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | yes | – |
No examples provided.
list-databases ~45
List all databases for a MongoDB connection
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| Name | Type | Req | Description |
|---|---|---|---|
| databases | array | yes | – |
| totalCount | number | yes | – |
No examples provided.
list-knowledge-sources ~43
List available data sources in the MongoDB Assistant knowledge base. Use this to explore available data sources or to find search filter parameters to use in search-knowledge.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mongodb-logs ~93
Returns the most recent logged mongod events
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| limit | integer | – | The maximum number of log entries to return. |
| type | string | – | The type of logs to return. Global returns all recent log entries, while startupWarnings returns only warnings and errors from when the process started. |
| Name | Type | Req | Description |
|---|---|---|---|
| logs | array | yes | – |
| shownCount | number | yes | – |
| totalLinesWritten | number | yes | – |
No examples provided.
rename-collection ~95
Renames a collection in a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| dropTarget | boolean | – | If true, drops the target collection if it exists |
| newName | string | yes | The new name for the collection |
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | – |
| newCollection | string | yes | – |
| oldCollection | string | yes | – |
| renamed | boolean | yes | – |
No examples provided.
search-knowledge ~171
Search for information in the MongoDB Assistant knowledge base. This includes official documentation, curated expert guidance, and other resources provided by MongoDB. Supports filtering by data source and version.
| Name | Type | Req | Description |
|---|---|---|---|
| dataSources | array | – | A list of one or more data sources to limit the search to. You can specify a specific version of a data source by providing the version label. If not provided, the latest version of all data sources… |
| limit | number | – | The maximum number of results to return |
| query | string | yes | A natural language query to search for in the MongoDB Assistant knowledge base. This should be a single question or a topic that is relevant to the user's MongoDB use case. |
No output schema declared.
No examples provided.
update-many ~150
Updates all documents that match the specified filter for a collection. If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider updating them in batches.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Collection name |
| connectionId | string | yes | The connection to run the operation against. Use the id returned by one of the connect tools. |
| database | string | yes | Database name |
| filter | object | – | The selection criteria for the update, matching the syntax of the filter argument of db.collection.updateOne() |
| update | object | yes | An update document describing the modifications to apply using update operator expressions |
| upsert | boolean | – | Controls whether to insert a new document if no documents match the filter |
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| database | string | yes | – |
| matchedCount | number | yes | – |
| modifiedCount | number | yes | – |
| upsertedCount | number | yes | – |
| upsertedId | string | – | – |
No examples provided.
How do I install the io.github.mongodb-js/mongodb-mcp-server server?
io.github.mongodb-js/mongodb-mcp-server runs locally as a container image, launched with docker run --rm -i -e MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAP -e MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MS -e MDB_MCP_ALLOW_REQUEST_OVERRIDES -e MDB_MCP_API_CLIENT_ID -e MDB_MCP_API_CLIENT_SECRET -e MDB_MCP_ASSISTANT_BASE_URL -e MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS -e MDB_MCP_CONFIRMATION_REQUIRED_TOOLS -e MDB_MCP_CONNECTION_IDLE_TIMEOUT_MS -e MDB_MCP_CONNECTION_SCOPE -e MDB_MCP_CONNECTION_STRING -e MDB_MCP_CONNECTION_STRINGS -e MDB_MCP_DANGEROUS_HOST_BINDING -e MDB_MCP_DISABLE_SERVER_SIDE_JS -e MDB_MCP_DISABLE_UNTRUSTED_DATA_WARNING -e MDB_MCP_DISABLED_TOOLS -e MDB_MCP_DRY_RUN -e MDB_MCP_ELICITATION_TIMEOUT_MS -e MDB_MCP_EVICTION_IDLE_GRACE_M_S -e MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS -e MDB_MCP_EXPORT_TIMEOUT_MS -e MDB_MCP_EXPORTS_PATH -e MDB_MCP_EXTERNALLY_MANAGED_SESSIONS -e MDB_MCP_HEALTH_CHECK_HOST -e MDB_MCP_HEALTH_CHECK_PORT -e MDB_MCP_HTTP_BODY_LIMIT -e MDB_MCP_HTTP_HEADERS -e MDB_MCP_HTTP_HOST -e MDB_MCP_HTTP_PORT -e MDB_MCP_HTTP_RESPONSE_TYPE -e MDB_MCP_IDLE_TIMEOUT_MS -e MDB_MCP_INDEX_CHECK docker.io/mongodb/mongodb-mcp-server:3.2.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/mongodb/mongodb-mcp-server
claude mcp add mongodb-js-mongodb-mcp-server -- docker run --rm -i -e MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAP -e MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MS -e MDB_MCP_ALLOW_REQUEST_OVERRIDES -e MDB_MCP_API_CLIENT_ID -e MDB_MCP_API_CLIENT_SECRET -e MDB_MCP_ASSISTANT_BASE_URL -e MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS -e MDB_MCP_CONFIRMATION_REQUIRED_TOOLS -e MDB_MCP_CONNECTION_IDLE_TIMEOUT_MS -e MDB_MCP_CONNECTION_SCOPE -e MDB_MCP_CONNECTION_STRING -e MDB_MCP_CONNECTION_STRINGS -e MDB_MCP_DANGEROUS_HOST_BINDING -e MDB_MCP_DISABLE_SERVER_SIDE_JS -e MDB_MCP_DISABLE_UNTRUSTED_DATA_WARNING -e MDB_MCP_DISABLED_TOOLS -e MDB_MCP_DRY_RUN -e MDB_MCP_ELICITATION_TIMEOUT_MS -e MDB_MCP_EVICTION_IDLE_GRACE_M_S -e MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS -e MDB_MCP_EXPORT_TIMEOUT_MS -e MDB_MCP_EXPORTS_PATH -e MDB_MCP_EXTERNALLY_MANAGED_SESSIONS -e MDB_MCP_HEALTH_CHECK_HOST -e MDB_MCP_HEALTH_CHECK_PORT -e MDB_MCP_HTTP_BODY_LIMIT -e MDB_MCP_HTTP_HEADERS -e MDB_MCP_HTTP_HOST -e MDB_MCP_HTTP_PORT -e MDB_MCP_HTTP_RESPONSE_TYPE -e MDB_MCP_IDLE_TIMEOUT_MS -e MDB_MCP_INDEX_CHECK docker.io/mongodb/mongodb-mcp-server:3.2.2
This image reads MDB_MCP_AGGREGATION_COUNT_MAX_TIME_MS_CAP, MDB_MCP_AGGREGATION_COUNT_TIMEOUT_MS, MDB_MCP_ALLOW_REQUEST_OVERRIDES, MDB_MCP_API_CLIENT_ID, MDB_MCP_API_CLIENT_SECRET, MDB_MCP_ASSISTANT_BASE_URL, MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS, MDB_MCP_CONFIRMATION_REQUIRED_TOOLS, MDB_MCP_CONNECTION_IDLE_TIMEOUT_MS, MDB_MCP_CONNECTION_SCOPE, MDB_MCP_CONNECTION_STRING, MDB_MCP_CONNECTION_STRINGS, MDB_MCP_DANGEROUS_HOST_BINDING, MDB_MCP_DISABLE_SERVER_SIDE_JS, MDB_MCP_DISABLE_UNTRUSTED_DATA_WARNING, MDB_MCP_DISABLED_TOOLS, MDB_MCP_DRY_RUN, MDB_MCP_ELICITATION_TIMEOUT_MS, MDB_MCP_EVICTION_IDLE_GRACE_M_S, MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS, MDB_MCP_EXPORT_TIMEOUT_MS, MDB_MCP_EXPORTS_PATH, MDB_MCP_EXTERNALLY_MANAGED_SESSIONS, MDB_MCP_HEALTH_CHECK_HOST, MDB_MCP_HEALTH_CHECK_PORT, MDB_MCP_HTTP_BODY_LIMIT, MDB_MCP_HTTP_HEADERS, MDB_MCP_HTTP_HOST, MDB_MCP_HTTP_PORT, MDB_MCP_HTTP_RESPONSE_TYPE, MDB_MCP_IDLE_TIMEOUT_MS and MDB_MCP_INDEX_CHECK. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.mongodb-js/mongodb-mcp-server server?
io.github.mongodb-js/mongodb-mcp-server is listed in the public MCP registry as io.github.mongodb-js/mongodb-mcp-server. MongoDB Model Context Protocol Server. This page covers its container image (docker.io/mongodb/mongodb-mcp-server).
Is the io.github.mongodb-js/mongodb-mcp-server server safe to use?
io.github.mongodb-js/mongodb-mcp-server scores 43 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 11 known advisories as of 5 November 2026. We do not grade that SBOM, as nothing verifies it. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mongodb-js/mongodb-mcp-server server expose?
io.github.mongodb-js/mongodb-mcp-server exposes 27 tools: aggregate-db, aggregate, collection-indexes, collection-schema, collection-storage-size, and 22 more. Their descriptions and schemas cost roughly 3,893 tokens of context every time the server is loaded.
Is the io.github.mongodb-js/mongodb-mcp-server server still maintained?
io.github.mongodb-js/mongodb-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.mongodb-js/mongodb-mcp-server server?
VerifyMCP ran 12 checks on io.github.mongodb-js/mongodb-mcp-server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.mongodb-js/mongodb-mcp-server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.