simple-db-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIMPLE_DB_MCP_MAX_ROWS | No | Maximum number of rows returned by execute_query. | 100 |
| SIMPLE_DB_MCP_READ_ONLY | No | Whether to enable read-only mode (true/false). | true |
| SIMPLE_DB_MCP_CONFIG_FILE | No | Path to a TOML configuration file for one or more named databases. | |
| SIMPLE_DB_MCP_DATABASE_URL | No | The SQLAlchemy async database URL for a single database (e.g., postgresql+asyncpg://user:pass@host/db). | |
| SIMPLE_DB_MCP_QUERY_TIMEOUT_SECONDS | No | Timeout in seconds for queries. | 30 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Return basic server health and non-sensitive configuration. |
| versionA | Return the server name and version. |
| ping_databaseB | Verify that the configured database connection works. |
| list_schemasC | List available database schemas. |
| list_tablesA | List tables and views in a schema. |
| describe_tableB | Describe columns and primary key metadata for a table. |
| execute_queryB | Execute a read-only SQL query with a configured row limit. |
| explain_queryB | Return the database query plan for a read-only SQL query. |
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
The tools are mostly distinct: list_schemas, list_tables, describe_table, execute_query, and explain_query each target a different aspect of database exploration. The health, version, and ping_database tools have overlapping purposes around server status, but their descriptions clarify the differences, so only minor confusion is possible.
Most tool names follow a clear verb_noun pattern (list_schemas, ping_database, execute_query). However, 'health' and 'version' are bare nouns, deviating from the otherwise consistent style. The underscore convention is uniform throughout, keeping the naming readable.
With 8 tools, the server is well-scoped for a simple database MCP. Each tool covers a necessary function—server diagnostics, schema/table introspection, and query execution/planning—without unnecessary bloat or skimping.
For a read-only database tool, the surface is complete: users can discover schemas, explore tables and columns, run queries, and inspect query plans. Health and version cover server metadata. No obvious gaps exist for the intended read-only scope.