Mongo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONGODB_URI | No | Mongo connection string | mongodb://localhost:27017 |
| DATABASE_NAME | No | Database name used by the server | mcpserver |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_connectionB | Check if MongoDB connection is active and healthy |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap in purpose. The tool 'check_connection' has a single, clear function, making it impossible for an agent to confuse it with any other tool.
The single tool name follows a consistent verb_noun pattern ('check_connection'), and with only one tool, there is no inconsistency in naming conventions. The naming is straightforward and predictable.
A single tool is too few for a MongoDB server, which typically requires CRUD operations, querying, indexing, and other database management tasks. This minimal set severely limits the server's utility and scope, indicating a significant mismatch with the expected domain coverage.
The tool set is severely incomplete for a MongoDB server. It lacks essential operations like insert, find, update, delete, or any other database interactions, leaving major gaps that will cause agent failures in performing typical database tasks. The single tool only handles connection checking, which is insufficient for the stated purpose.