MongoDB
Arcade Optimized
Tools to query and explore a MongoDB database
Author:Arcade
Version:
1.1.2Auth:No authentication required
6tools
6require secrets
MongoDB Toolkit
Provides tools for querying and exploring a MongoDB instance from within Arcade — covering database/collection discovery, document retrieval, aggregation, and schema inference.
Capabilities
- Discovery: Enumerate all databases in a MongoDB instance and all collections within a given database, establishing the context needed before any query.
- Schema inference: Sample documents from a collection to infer field names and data types, a required step before running queries against schema-less MongoDB collections.
- Document retrieval & counting: Find documents with filtering, projection, and sorting; count matching documents using arbitrary filter expressions.
- Aggregation pipelines: Execute multi-stage pipelines (
$match,$group,$project,$sort,$limit,$lookup, etc.) for complex data processing and cross-collection joins.
Secrets
MONGODB_CONNECTION_STRING — The full MongoDB connection URI used to authenticate and connect to your MongoDB instance. It follows the standard format mongodb://[username:password@]host[:port][/database][?options] or mongodb+srv://... for Atlas clusters. To obtain it:
- MongoDB Atlas: Log in to Atlas, navigate to your cluster, click Connect, choose your connection method (e.g., Drivers), and copy the generated connection string. You will need to embed your database username and password (created under Database Access) into the URI, and ensure your IP or Arcade's egress IPs are allowlisted under Network Access.
- Self-hosted MongoDB: Construct the URI from your host, port, and credentials as configured in your
mongodinstance or your authentication backend.
Store this value as a secret in Arcade by following the Arcade secrets guide. You can 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