DB Analyzer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | SQL Server hostname | |
| DB_PORT | No | SQL Server port | 1433 |
| DB_USER | Yes | Database username | |
| DB_ENCRYPT | No | Enable connection encryption | true |
| DB_DATABASE | No | Default database (optional) | |
| DB_PASSWORD | Yes | Database password | |
| DB_POOL_MAX | No | Maximum connection pool size | 10 |
| DB_TRUST_SERVER_CERT | No | Trust server certificate | true |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ping_dbD | – |
| execute_queryD | – |
| execute_non_queryD | – |
| execute_stored_procedureD | – |
| list_databasesD | – |
| list_schemasD | – |
| list_tablesD | – |
| get_table_columnsD | – |
| get_indexesD | – |
| analyze_schema_healthD | – |
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 10 tools
Tool names clearly indicate distinct operations: ping for connectivity, query vs non-query for different statement types, stored procedure for SP calls, and list/get for schema introspection. Minor ambiguity exists between execute_query and execute_non_query, but they are standard distinct categories.
All tool names follow a consistent snake_case verb_noun pattern (e.g., ping_db, execute_query, list_tables, get_indexes). No mixed conventions or vague verbs.
The server has 10 tools, which is well within the ideal range for a database analyzer. Each tool covers a clear aspect of database interaction and introspection, earning its place without bloat.
The tool surface covers essential database operations: connectivity, query execution, schema object listing (databases, schemas, tables, columns, indexes), and schema health analysis. Minor gaps like constraint or foreign key introspection exist, but core analysis and execution workflows are well represented.