
Mongo Scout Mcp
io.github.bluworkPublished by GitHub account bluworkv1.0.3Updated Oct 24, 2026
Scout your MongoDB databases with AI - safety features, live monitoring, and data quality
Overview
Lets an assistant explore, query, monitor, and diagnose MongoDB databases, with data-quality checks and optional guarded writes.
- What you can do
- Mongo Scout MCP connects an assistant to a MongoDB instance and exposes roughly 50 tools grouped into exploration, querying, diagnostics, monitoring, data quality, relationships, time series, indexes, export, preview, and write operations. Typical tools include listCollections, inferSchema, find, aggregate, detectVolumeAnomalies, findDuplicates, findOrphans, getServerStatus, getLiveMetrics, exportCollection, and previewUpdate or previewDelete. It runs read-only by default, and write tools such as insertOne, updateMany, deleteMany, bulkWrite, and dropCollection are available only when a read-write instance is started.
- When to use it
- Worth adding when an assistant needs to inspect or analyze a MongoDB database directly: understanding collections and schemas, running queries and aggregations, checking data quality such as duplicates, orphans, missing fields, or inconsistent types, watching server and query performance, or exporting collections. It is also useful for previewing changes before applying them.
- Requirements
- A local Node.js runtime, since it is distributed as the npm package mongo-scout-mcp and started over stdio. A MongoDB connection string and a target database name are passed as command arguments. Optional environment variables ENABLE_LOGGING and LOG_DIR control file logging. Write access requires starting a separate instance with the read-write flag.
Installation
In SourceWeft
- Open Mongo Scout Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Mongo Scout MCP
Scout your MongoDB databases with AI - A production-ready Model Context Protocol server with built-in safety features, live monitoring, and data quality tools.
What You Get
You ask:
"Anything unusual happening with order volume this month?"
Mongo Scout returns:
Volume Analysis: orders
Statistics (last 30 days)
Anomalies Detected
- Feb 14 — 5,892 documents (+7.4σ) — Valentine's Day spike
- Feb 22 — 847 documents (-4.9σ) — Payment gateway outage window
- Mar 1 — 4,201 documents (+3.3σ) — Month-start subscription renewals
Recommendations
- Feb 22 drop warrants investigation — possible data loss during outage
- Consider auto-scaling rules for predictable spikes (month boundaries, holidays)
- Set up alerts for volumes exceeding ±3σ from rolling average
That's detectVolumeAnomalies — one of 50 tools covering exploration, querying, diagnostics, monitoring, data quality, and safe writes.
Quick Start
Claude Code
Then ask: "What collections do I have and what do their schemas look like?"
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Cursor / VS Code
Add to your MCP settings:
Read-Only vs Read-Write
The server runs in read-only mode by default. For write operations, run a separate instance:
- mongo-scout-readonly: Safe exploration, no risk of data modification
- mongo-scout-readwrite: Write operations when explicitly needed
Tools
Explore — understand your database
listDatabases— all databases in the instancegetDatabaseStats— storage and performance statisticslistCollections— collections in the current databasegetCollectionStats— size, document count, index detailsinferSchema— schema inference from sampled documents
Query — find and analyze documents
find— query documents with filtering, sorting, projectionaggregate— run aggregation pipelinescount— count documents matching a querydistinct— unique values for a fieldtextSearch— full-text search across indexed fieldsexplainQuery— query execution plan analysis
Diagnose — spot problems early
detectVolumeAnomalies— unusual patterns in document volumeanalyzeQueryPerformance— query optimization using explain plans
Monitor — watch it live
getServerStatus— server performance metricsgetCurrentOperations— currently running operationsgetConnectionPoolStats— connection pool healthgetProfilerStats— profiler data and slow operationsgetLiveMetrics— real-time metrics with continuous updatesgetHottestCollections— collections with highest activitygetCollectionMetrics— detailed per-collection metricsgetSlowestOperations— slow query trackingrunAdminCommand— execute admin commands
Data Quality — trust your data
findDuplicates— duplicate documents by field combinationfindOrphans— orphaned references across collectionsfindMissingFields— documents missing required fieldsfindInconsistentTypes— type inconsistencies across documentsvalidateDocuments— custom validation with MongoDB$expr
Relationships — follow the references
exploreRelationships— multi-hop relationship traversal
Time Series — temporal analysis
findRecent— documents within a time windowfindInTimeRange— date range queries with optional grouping
Indexes — manage your indexes
listIndexes— all indexes for a collectioncreateIndex— create new indexesdropIndex— remove indexes
Export — get data out
exportCollection— JSON, JSONL, or CSVcloneCollection— clone with filtering and index copying
Preview — dry-run before changing anything
previewUpdate/previewDelete— see what would change before committingpreviewBulkWrite— preview bulk operations
Write (read-write only) — safe modifications
insertOne/insertMany— insert documentsupdateOne/updateMany— update with dryRun and maxDocuments limitsreplaceOne— replace a single documentfindOneAndUpdate— find and update atomicallydeleteOne/deleteMany— delete with dryRun and maxDocuments limitsbulkWrite— multiple write operations in one callrenameField— rename fields with dry-run and index migrationcreateCollection/dropCollection— collection management
Security
- Read-only by default — write operations must be explicitly enabled
- All queries are validated and sanitized
- MongoDB operator injection protection
- Connection string credential redaction in logs
- Rate limiting on all operations
- Response size limits to prevent memory exhaustion
Examples
"What collections do I have and what's the schema of users?"
"Find duplicate emails in the users collection."
"Show me order volume anomalies over the last month."
"What's happening on the server right now?"
"Find orders that reference deleted users."
"Export the products collection as CSV."
Configuration
CLI flags: --read-only (default), --read-write, --mode <mode>
Logging
File logging is disabled by default. Set ENABLE_LOGGING=true to enable. Two log files are created in LOG_DIR:
- tool-usage.log — every tool call with timestamp, name, and arguments
- error.log — errors with stack traces
Connection strings are automatically redacted in all output.
ObjectId Format
Both formats accepted:
Development
License
Apache-2.0
Source: README.md at commit 09e3774
Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts