mcp-sqlserver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSSQL_MCP_CONNECTIONS | No | Path to a connections.json file (alternative to the default location). | |
| MSSQL_MCP_CONNECTIONS_JSON | No | Inline JSON string containing the connections configuration. |
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 |
|---|---|
| list_connectionsA | List all available SQL Server connections grouped by connectionGroup |
| reload_connectionsA | Reload connections from connections.json file without restarting the MCP server. Closes existing connection pools and loads new configuration. |
| queryC | Execute a SQL query on the database |
| get_schemaB | Get database schema information for specific tables |
| get_indexesB | Get index information for a table |
| get_execution_planB | Get execution plan for a query |
| get_stored_procedureC | Get stored procedure definition |
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
Each tool serves a distinct purpose: query executes SQL, get_schema retrieves table schemas, get_indexes gets index info, get_execution_plan analyzes query plans, get_stored_procedure fetches procedure definitions, list_connections enumerates connections, and reload_connections refreshes configuration. No overlap or ambiguity.
Tool names follow a consistent verb_noun pattern: get_* for retrieval of specific metadata, list_ for enumeration, reload_ for refreshing, and query as a direct verb. All names are snake_case and predictable.
7 tools is well within the ideal 3-15 range for a SQL Server MCP server. Each tool addresses a core need (querying, schema inspection, performance analysis, connection management) without redundancy.
The surface covers query execution and common metadata operations (schema, indexes, execution plans, stored procedures) plus connection management. Minor gap: no direct 'list tables' or 'list databases' tool, but these can be obtained via query, so it's a workable gap.