mssql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_tablesB | Lista las tablas de la base de datos, con su esquema y cantidad aproximada de filas. Permite filtrar por patrón de nombre. |
| get_table_definitionB | Devuelve columnas, tipos, nulabilidad, primary key, foreign keys e índices de una tabla. |
| list_viewsC | Lista las vistas de la base de datos. |
| list_triggersB | Lista los triggers, indicando la tabla a la que pertenecen y los eventos que disparan. |
| list_stored_proceduresC | Lista los stored procedures de la base de datos. |
| get_object_definitionB | Devuelve el código T-SQL completo de un stored procedure, vista o trigger, y sus parámetros si es un SP. Úsala para analizar un SP y proponer ajustes. |
| get_object_dependenciesA | Lista los objetos (tablas, vistas, otros SPs) referenciados por un SP, vista o trigger — útil para entender el impacto antes de modificarlo. |
| run_select_queryB | Ejecuta una consulta SELECT de solo lectura (máximo 500 filas). No se permite INSERT/UPDATE/DELETE/DDL/EXEC. |
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
Each tool targets a distinct resource type (tables, views, triggers, SPs) or action (list, get definition, get dependencies, run query). get_table_definition and get_object_definition are separated clearly for tables vs. code objects. No overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern: list_* for enumerating objects, get_* for retrieving definitions/dependencies, and run_select_query for queries. The naming is predictable and uniform.
With 8 tools, the server is well-scoped for its purpose: browsing database metadata and running read-only queries. Each tool earns its place and the count is neither too thin nor overwhelming.
The tool set covers the full read-only lifecycle: listing all object types, retrieving table schemas and code definitions, analyzing dependencies, and executing SELECT queries. There are no obvious gaps for the stated domain of database exploration.