Custom MCP Database Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| db_list_aliasesA | List every configured database alias and its type. Returns: {"aliases": [{"alias": str, "type": "postgres|mysql|mongo|oracle"}, ...]} |
| db_list_collectionsA | List all collections for a configured MongoDB alias. Returns: {"collections": [str, ...]} |
| db_execute_queryA | Run a query against a configured database. SQL (postgres/mysql/oracle): pass the SQL string in MongoDB: pass a JSON filter object in Returns: {"data": [...], "row_count": int} (plus "error" on a rejected empty Mongo filter) |
| db_security_statusA | Report the active security policy. Returns: {"readonly": bool, "allow_writes": bool, "allow_ddl": bool, "max_rows": int, "mongo_javascript_blocked": bool} |
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 4 tools
Each tool targets a distinct function: listing aliases, listing MongoDB collections, executing queries, and reporting security status. No overlap or ambiguity.
All tools follow a 'db_' prefix and mostly verb_noun pattern (db_list_aliases, db_list_collections, db_execute_query), though db_security_status is noun_noun, creating a minor inconsistency.
With 4 tools, the set is small but well-scoped for a basic database query utility. It does not feel excessive or obviously insufficient for its stated purpose.
The tool set lacks essential operations like creating or modifying aliases, listing tables for SQL databases, and managing schema. The single query tool covers multiple DB types but misses common CRUD operations, leaving notable gaps.