SQL Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | The host address of the MSSQL database server | localhost |
| DB_PORT | Yes | The port number of the MSSQL database server | 1433 |
| DB_DATABASE | Yes | The name of the MSSQL database to connect to | |
| DB_PASSWORD | Yes | The password for connecting to the MSSQL database | |
| DB_USERNAME | Yes | The username for connecting to the MSSQL database |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tablesB | Get a list of all tables in the database |
| get-tableC | Get a specific table by name |
| get-stored-proceduresB | Get a list of all stored procedures in the database |
| get-stored-procedureC | Get a specific stored procedure by name |
| queryC | Query the database with a SQL statement |
| start-transactionC | Start a new transaction |
| commit-transactionC | Commit a transaction |
| rollback-transactionC | Rollback a transaction |
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
Every tool has a clearly distinct purpose with no ambiguity. Tools are clearly separated by resource type (tables vs stored procedures) and action type (get specific vs get list vs transaction operations vs query). The query tool stands alone as a general-purpose operation.
All tools follow a consistent verb-noun pattern with hyphens. Transaction tools use verb-transaction pattern (start-transaction, commit-transaction, rollback-transaction), get operations use get-noun pattern (get-table, get-tables), and query stands alone as a clear single verb. The naming is perfectly predictable throughout.
8 tools is well-scoped for a database server. Each tool earns its place with clear responsibilities: 4 for data/metadata retrieval, 3 for transaction management, and 1 for general querying. This provides comprehensive coverage without bloat.
The toolset covers core database operations well with querying, transaction management, and metadata retrieval. Minor gaps exist in write operations beyond transactions (no explicit insert/update/delete tools) and schema modification (no create/alter/drop tools), but the query tool provides a workaround for most of these operations.