DB-Explorer-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind the HTTP server to when using MCP_TRANSPORT=streamable-http (e.g., 0.0.0.0). | |
| MCP_PORT | No | Port to bind the HTTP server to when using MCP_TRANSPORT=streamable-http (e.g., 8000). | |
| DATABASE_URL | No | SQLAlchemy database URL. Defaults to a local SQLite database. Examples: sqlite:///C:/data/example.db, postgresql+psycopg2://user:password@localhost:5432/example, mysql+pymysql://user:password@localhost:3306/example | sqlite:///sample.db |
| MCP_TRANSPORT | No | Transport for the MCP server. If set to 'streamable-http', enables HTTP hosting. Defaults to stdio if not set. |
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 |
|---|---|
| explore_schemaA | Explore database tables, columns, keys, indexes, and sample rows. |
| execute_queryB | Execute one validated, read-only SQL SELECT query. |
| explain_queryA | Return the database execution plan for one safe SELECT query. |
| validate_schemaC | Check tables for missing primary keys and unindexed foreign keys. |
| suggest_indexB | Suggest indexes from a query plan or table foreign-key metadata. |
| migration_contextB | Return schema context for client-side migration generation. |
| validate_migrationA | Validate migration scripts without executing them. |
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 7 tools
Most tools have distinct purposes: exploring, executing, explaining, validating, and suggesting indexes are clearly separate. The main overlap risk is between explore_schema and migration_context, since both provide schema context, but their intended use cases differ enough to avoid serious confusion.
Six of seven tools follow a clean verb_noun pattern (explore_schema, execute_query, explain_query, validate_schema, suggest_index, validate_migration). migration_context breaks the pattern by being a noun phrase, but the overall naming style remains predictable and readable.
With 7 tools, the server is well-scoped for the stated purpose of database exploration, query execution, and migration validation. Each tool addresses a meaningful workflow step without unnecessary bloat.
The toolset covers the core read-only database workflows: schema inspection, query validation/execution/explanation, structural tenant-focused checks, index suggestions, and migration validation. No obvious dead-end exists for the server's stated purpose.