mssql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | HTTP listen port | 3000 |
| MCP_TRANSPORT | No | Force stdio or http mode. If unset, auto-detects. | |
| DB_CONNECTIONS | Yes | JSON array of {name, host, port?, database, user, password} objects |
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_databasesA | 列出此 MCP 服務已設定的所有資料庫連線名稱 |
| list_tablesA | 列出指定資料庫中所有的 TABLE 和 VIEW，包含欄位名稱、型別、是否可為 NULL |
| lookupA | 在指定的 TABLE 或 VIEW 中以關鍵字模糊搜尋（LIKE），最多回傳 100 筆 |
| query_sqlA | 執行自由 SELECT 語句查詢指定資料庫（僅允許 SELECT，禁止 INSERT/UPDATE/DELETE 等異動語法） |
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 4 tools
Each tool has a unique and clearly distinct purpose: listing databases, listing tables with schema, performing keyword searches, and executing arbitrary SQL queries. There is no ambiguity or overlap.
All tool names follow a consistent verb_noun pattern in snake_case (list_databases, list_tables, lookup, query_sql). Even 'lookup' is a common verb that fits the pattern.
With 4 tools, the set is well-scoped for a read-only database server. It provides essential introspection and data access without being bloated or too sparse.
The tools cover listing databases, tables with schema, keyword search, and arbitrary SELECT queries, which is fairly complete for read-only access. However, a direct tool to fetch a single record by primary key is missing, though lookup can serve that purpose.