Caplets Catalog
official
spiritledsoftware/caplets

MongoDB

Inspect MongoDB databases, collections, schemas, indexes, queries, and Atlas resources through MongoDB's MCP server with read-only access by default.

Install
caplets install spiritledsoftware/caplets mongodb

Inspect before installing

  • Local controlThis Caplet can operate against local project or machine state.
  • Setup requiredThis Caplet includes setup steps that should be completed before use.
CAPLET.md

Frontmatter

FieldValue
nameMongoDB
descriptionInspect MongoDB databases, collections, schemas, indexes, queries, and Atlas resources through MongoDB's MCP server with read-only access by default.
avoidWhenAvoid when the work only concerns local ODM models, migrations, or application code rather than live MongoDB or Atlas state.
tagsmongodb, atlas, database, queries, nosql
catalog.iconhttps://www.mongodb.com/favicon.ico
setup.verify[0].labelCheck Node.js is available
setup.verify[0].commandnode
setup.verify[0].args--version
setup.verify[1].labelCheck npx is available
setup.verify[1].commandnpx
setup.verify[1].args--version
mcpServer.commandnpx
mcpServer.args-y, mongodb-mcp-server@latest, --readOnly
mcpServer.env.MDB_MCP_CONNECTION_STRING$vault:MDB_MCP_CONNECTION_STRING
mcpServer.startupTimeoutMs100000
mcpServer.callTimeoutMs300000

MongoDB

Query Scope

Before querying data, establish the cluster, database, collection, Atlas project, environment, and read-only intent. Schema samples, indexes, query plans, and collection metadata provide context for proposed query or index changes. Small result windows and projections limited to necessary fields reduce exposure.

Safe Operation

  • The catalog entry starts MongoDB MCP with --readOnly and a Vault-backed connection string by default.
  • Removing --readOnly, changing credentials, writing data, changing indexes, or performing Atlas actions requires review of the proposed target and effect.
  • MongoDB data can contain production records, PII, secrets, and customer information. Broad scans should be avoided, and sensitive fields should be redacted from summaries.
  • Atlas API access should use least-privilege Atlas service account credentials instead of a database connection string.