mcp-mssql-secure
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSSQL_HOST | Yes | Database host (required). | |
| MSSQL_PORT | No | Database port (default: 1433). | 1433 |
| MSSQL_USER | Yes | SQL authentication login (required). | |
| MSSQL_ENCRYPT | No | Enable TLS encryption (default: true). Use 'true' or 'false'. | true |
| MSSQL_DATABASE | Yes | Database name (required). | |
| MSSQL_PASSWORD | Yes | SQL authentication password (required). | |
| MSSQL_ACCESS_MODE | No | Access mode: 'readonly' (default), 'dml', or 'full'. Can be overridden by --access-mode CLI flag. | readonly |
| MSSQL_LOCK_CONNECTION | No | Disables connect_db at runtime when true (default: true when env config is set). Use 'true' or 'false'. | true |
| MSSQL_TRUST_SERVER_CERTIFICATE | No | Trust self-signed certificates (default: false). Use 'true' or 'false'. Recommended for on-prem dev with self-signed certs. | false |
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 |
|---|---|
| connect_dbD | Disabled when MSSQL_LOCK_CONNECTION=true (use environment variables instead) |
| queryA | Execute a read-only SQL query (SELECT, WITH, EXPLAIN, TABLE, VALUES) |
| list_schemasA | List all schemas in the database |
| list_tablesC | List tables in the database |
| describe_tableC | Get table structure |
| list_programmable_objectsA | List stored procedures, functions, views, and triggers (read-only metadata) |
| describe_programmable_objectA | Get full T-SQL definition and parameters for a stored procedure, function, view, or trigger (read-only; does not execute) |
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 for ad-hoc read-only SQL, list_tables and list_schemas for enumeration, describe_table for table structure, and programmable-object tools for stored procedures/functions/views/triggers. No overlapping boundaries that would confuse an agent.
Tool names follow a clear verb_noun pattern: list_* for enumeration, describe_* for metadata, and query/connect_db as simple verbs. Consistent snake_case throughout.
Seven tools is a well-scoped size for a read-only database exploration server, covering querying, listing, and describing without unnecessary bloat or missing essentials.
The surface fully covers read-only database exploration: execute queries, discover tables/schemas/programmable objects, and inspect their definitions. No obvious dead ends for typical inspection workflows.