MongoDB
Community
Tools to query and explore a MongoDB database
Author:Arcade
Version:
1.1.0Auth:No authentication required
6tools
6require secrets
MongoDB Toolkit
The Arcade MongoDB toolkit connects agents to a MongoDB instance, enabling programmatic discovery, inspection, and querying of databases and collections.
Capabilities
- Discovery & introspection — enumerate available databases, list all collections within a database, and sample documents to infer a collection's schema (field names and types) before querying.
- Document retrieval & filtering — find documents with full MongoDB query-operator support (
$gte,$lte,$in,$regex, etc.), with control over projection, sort order, and result limits. - Aggregation pipelines — execute multi-stage pipelines (
$match,$group,$project,$sort,$limit,$lookup, and more) for complex data processing and cross-collection joins. - Document counting — count documents matching any filter expression without fetching document payloads.
Secrets
MONGODB_CONNECTION_STRING
A standard MongoDB connection URI (e.g., mongodb://user:password@host:port/database or an Atlas SRV URI mongodb+srv://...) that includes credentials, host(s), and optionally a default database and TLS/auth options.
- Self-hosted MongoDB — construct the URI from your host, port, and the username/password of a database user with at least read privileges on the target databases. See the MongoDB connection string docs for URI format details.
- MongoDB Atlas — in the Atlas UI, go to your cluster → Connect → Drivers, choose your driver version, and copy the generated SRV connection string. Replace
<password>with the Atlas database user's password. The database user must have at minimum a built-in Read Any Database role or a custom role withfindandlistCollectionsprivileges on the relevant databases. Atlas free-tier clusters are supported.
Store this value as an Arcade secret; see Arcade secret configuration docs or manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(6)
6 of 6 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Execute a MongoDB aggregation pipeline on a collection.
ONLY use this tool if you have already loaded the schema of the collection you need to query.
Load the collection's schema first if it is not already known.
Returns a list of JSON strings, where each string represents a
result document from the aggregation
(tools cannot return complex types).
Aggregation pipelines allow for complex data processing including:
* $match - filter documents
* $group - group documents and perform calculations
* $project - reshape documents
* $sort - sort documents
* $limit - limit results
* $lookup - join with other collections
* And many more stages | 1 | ||
Count documents in a MongoDB collection matching the given filter. | 1 | ||
Discover all the collections in the MongoDB database.
Use when the list of collections is not known.
ALWAYS use this tool before any other tool that requires a collection name. | 1 | ||
Discover all the databases in the MongoDB instance. | 1 | ||
Find documents in a MongoDB collection.
ONLY use this tool if you have already loaded the schema of the collection you need to query.
Load the collection's schema first if it is not already known.
Returns a list of JSON strings, where each string represents a
document from the collection (tools cannot return complex types).
When running queries, follow these rules which will help avoid errors:
* Always specify projection to limit fields returned if you don't need all data.
* Always sort your results by the most relevant fields first. Use '_id' if you're unsure.
* Use appropriate MongoDB query operators for complex filtering ($gte, $lte, $in, $regex, etc.).
* Be mindful of case sensitivity when querying string fields.
* Use indexes when possible (typically on _id and commonly queried fields). | 1 | ||
Get the schema/structure of a MongoDB collection by sampling documents.
Since MongoDB is schema-less, this tool samples a configurable number of documents
to infer the schema structure and data types.
This tool should ALWAYS be used before executing any query.
All collections in the query must be discovered first by listing the database's collections. | 1 |
Last updated on