Multi-Database CRUD MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_BACKEND | No | The database backend to use: 'sqlite' or 'postgresql' | |
| SQLITE_PATH | No | Path to the SQLite database file (only for SQLite backend) | |
| DATABASE_URL | No | PostgreSQL connection URL (only for PostgreSQL backend) |
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 |
|---|---|
| database_healthA | Check the selected database backend and its connection. |
| create_productB | Create one product. Price and stock must be zero or greater. |
| get_productA | Read one product by its positive numeric ID. |
| list_productsA | List products with pagination. Limit is between 1 and 100. |
| update_productC | Replace the editable fields of an existing product. |
| delete_productA | Permanently delete one product by ID. Confirm user intent first. |
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 6 tools
Each tool has a clearly distinct purpose: health check, create, get, list, update, delete. No overlapping functionality or ambiguity between tools.
CRUD tools follow a consistent verb_noun pattern (create_product, get_product, list_products, update_product, delete_product). database_health breaks the pattern by being noun-only, but it is a single minor deviation.
Six tools is well-scoped for a CRUD server with a health check. Each tool earns its place with no unnecessary additions.
The tool set covers the full product lifecycle: create, read (single and list), update, and delete. The health check adds operational coverage. No obvious gaps for the stated purpose.