MongoDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONGODB_URI | Yes | MongoDB connection string (e.g. mongodb://localhost:27017 or mongodb+srv://...) |
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 |
|---|---|
| list_databasesA | List all databases on the connected MongoDB instance |
| list_collectionsA | List all collections in a given database |
| list_indexesB | List all indexes on a collection |
| run_aggregationC | Run an aggregation pipeline on a collection |
| run_aggregation_to_fileA | Run an aggregation pipeline on a collection and write results to a JSON file on disk. Returns only metadata (document count, file path, file size) instead of the actual documents, which avoids loading large result sets into the context window. Use CLI tools like jq, head, or the Read tool to selectively inspect the output file. |
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 5 tools
Each tool targets a distinct operation: listing databases, collections, indexes, running aggregations, and running aggregations to file. The two aggregation tools are clearly differentiated by output method and purpose.
All tool names follow a consistent verb_noun pattern (list_* for enumeration, run_* for execution). No mixing of conventions or vague verbs.
Five tools is well-scoped for a focused MongoDB utility server. Each tool earns its place without redundancy or excessive breadth.
The set covers listing and aggregation but lacks common MongoDB operations such as find/query, insert, update, and delete. This leaves significant gaps for typical database usage, forcing agents to work around missing functionality.