MCP MS SQL Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_USER | Yes | Your database username | |
| DB_SERVER | Yes | Your MS SQL Server address | |
| DB_PASSWORD | Yes | Your database password | |
| DB_DATABASE_NAME | Yes | Your database name |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sql_queryC | Execute a SQL query against the MS SQL Server database |
| list_tablesA | List all tables in the database |
| describe_tableB | Get the schema information for a specific table |
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 3 tools
Each tool has a clear, distinct purpose: listing tables, describing a table's schema, and executing arbitrary SQL queries. There is no overlap or ambiguity.
All tool names follow a consistent snake_case verb_noun pattern: list_tables, describe_table, execute_sql_query. No deviations.
Three tools is minimal but well-scoped for a simple database interface covering exploration and querying. It avoids unnecessary complexity.
The set lacks explicit tools for DDL (create/alter/drop), DML (insert/update/delete), or transaction control, but the execute_sql_query tool can compensate. Notable gaps exist but are workable.