mongo-readonly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONGO_READONLY_PROFILES | No | Path to the profiles configuration file. Config lookup order is $MONGO_READONLY_PROFILES, then ./profiles.yaml, then ~/.mongo-readonly/profiles.yaml; the first existing file wins. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mongo_list_profilesA | List named MongoDB connections with host, port, and database; no credentials. |
| mongo_findC | Read documents from a profile. Default limit 100, maximum 1000. |
| mongo_find_oneC | Read one matching document from a profile. |
| mongo_countC | Count matching documents in a profile's collection. |
| mongo_aggregateB | Run a read-only aggregation; $out and $merge are forbidden. Default result limit 100, maximum 1000. |
| mongo_distinctB | Read distinct field values in a profile's collection. |
| mongo_list_collectionsB | List collection names in a profile's database. |
| mongo_collection_statsC | Read collection statistics from a profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a distinct read operation (find, find_one, count, distinct, aggregate, list_collections, list_profiles, collection_stats) and the descriptions make the boundaries clear. The only real overlap is mongo_aggregate, which can replicate find/count work, but the stated limits and forbidden stages keep it reasonably separable.
All tools share a uniform mongo_ prefix and follow a verb_object pattern (mongo_find, mongo_list_profiles, mongo_count). The lone deviation is mongo_collection_stats, which is noun-only rather than verb-first, but it remains readable and predictable.
Eight tools is a well-scoped surface for a read-only MongoDB server, covering the core query verbs plus connection and collection discovery. Nothing feels redundant or padded, and there is no obvious operation an agent would expect that is missing from this count.
For a documented read-only server, coverage is strong: connectivity discovery, collection enumeration, document reads, counts, distincts, aggregations, and stats. Minor gaps exist around query-planning/explain, index inspection, and database-level listing, but agents can work around these for typical read workflows.