MSSQL MCP Reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_NAME | Yes | SQL Server hostname/IP | |
| SCRIPTS_PATH | No | Path to named SQL scripts directory | |
| SQL_PASSWORD | No | Password for SQL or Windows auth (required if SQL_AUTH_MODE is sql or windows) | |
| SQL_USERNAME | No | Username for SQL or Windows auth (required if SQL_AUTH_MODE is sql or windows) | |
| DATABASE_NAME | Yes | Target database | |
| SQL_AUTH_MODE | No | Authentication mode: sql, windows, or aad | aad |
| AUDIT_LOG_PATH | No | Custom audit log path | |
| ENVIRONMENTS_CONFIG_PATH | No | Path to multi-environment JSON config |
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 |
|---|---|
| read_dataA | Executes a read-only SELECT query. Auto-limits results if no TOP clause present. Blocks destructive operations. |
| list_tablesA | Lists tables in an MSSQL Database, optionally filtered by schema. For server-level access environments, you can specify a database to list tables from. |
| list_databasesA | Lists databases on the SQL Server instance. Requires server-level access. Filtered by environment policies. |
| list_environmentsA | Lists all configured database environments available for connection. Shows environment names, descriptions, access levels, and policy restrictions. Use this to discover which environments are available before running queries. |
| validate_environment_configA | Validates the environments.json configuration file for correctness and security best practices. Checks include:
Returns validation results for each environment with errors and warnings. |
| list_scriptsB | Lists available named SQL scripts. Scripts are pre-approved SQL templates that can be executed with parameters. |
| run_scriptA | Executes a named SQL script with parameters. Scripts are pre-approved SQL templates. Use list_scripts to see available scripts. |
| describe_tableB | Describes the schema (columns and types) of a specified MSSQL Database table. For server-level access environments, you can specify a database to target. |
| search_schemaC | Searches tables and columns using wildcard patterns to discover schema names. |
| profile_tableA | Profiles a table by analyzing column statistics, data distributions, and sample records. Returns metadata, cardinality info, null counts, and representative samples for each column. |
| inspect_relationshipsA | Describes inbound and outbound foreign-key relationships for a given table, including column mappings and referential actions. |
| inspect_dependenciesA | Shows what database objects depend on a table, view, or other object. Use for impact analysis before schema changes. |
| test_connectionC | Tests connectivity to a database environment and returns status, latency, and basic server info. |
| explain_queryA | Generates an estimated execution plan (SHOWPLAN_XML) for a SQL query without executing it. |
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 14 tools
Each tool targets a distinct database operation or analysis aspect. Even closely related tools like profile_table and describe_table serve different purposes (schema vs. statistics). There is no ambiguity between tools.
All tool names follow a consistent verb_noun pattern with lowercase underscores. Verbs are clear and descriptive (list, describe, explain, inspect, profile, etc.), making it easy to predict functionality.
With 14 tools, the server covers a broad but focused range of database read and analysis operations without being overwhelming or sparse. This count is well-suited for a specialized database reader server.
The tool set covers schema discovery, data querying, dependency analysis, and configuration management. However, it lacks tools for listing other database objects like views, stored procedures, or indexes, which may be needed for thorough analysis.