mssql-mcp
Read-only MCP server for Microsoft SQL Server that retrieves connection details from AWS Secrets Manager, enabling database exploration and querying via natural language.
README
mssql-mcp
A read-only Microsoft SQL Server MCP server using connection details from AWS Secrets Manager at tool-call time — nothing is read from disk or environment variables except the secret reference itself.
Cross-platform: it's a pure-JavaScript MCP server (no native or ODBC
dependencies), so it runs identically on macOS, Linux, and Windows via
npx.
Configure in .claude.json
{
"mcpServers": {
"my-db": {
"command": "npx",
"args": ["-y", "@dhipskind253/mssql-mcp"],
"env": {
"AWS_ACCOUNT_ID": "123456789012",
"SECRET_NAME": "my-aws-secret",
"AWS_REGION": "us-east-1",
"TRUST_SERVER_CERTIFICATE": "false"
}
}
}
}
| Env var | Required | Default | Description |
|---|---|---|---|
AWS_ACCOUNT_ID |
yes | — | The AWS account where the secret lives. Combined with name + region into a full ARN. |
SECRET_NAME |
yes | — | The Secrets Manager secret name (no ARN suffix needed). |
AWS_REGION |
yes | — | AWS region the secret is in (e.g. us-east-1). Also picked up by the AWS SDK as its default region. |
TRUST_SERVER_CERTIFICATE |
no | false |
Skip TLS cert validation to the SQL Server. Accepts true/false/1/0/yes/no. Set true only if you understand why. |
Standard AWS SDK env vars (AWS_PROFILE, AWS_ACCESS_KEY_ID, etc.) are
honored via the default credential provider chain. Most users just need
aws sso login to be current.
Required secret JSON
The secret value must be a JSON document with at least these fields:
{
"host": "myserver.database.windows.net",
"port": 1433,
"database": "mydb",
"username": "ro_user",
"password": "..."
}
database may also be supplied as dbname — the field name AWS uses
in its built-in RDS-credentials secret template. If both are present,
database wins.
Optional fields (with defaults shown):
| Field | Default | Notes |
|---|---|---|
port |
1433 |
|
encrypt |
true |
TLS to the server. |
TLS cert trust is not read from the secret — set
TRUST_SERVER_CERTIFICATEin the MCP server'senvblock instead. AnytrustServerCertificatefield in the secret JSON is ignored.
Read-only by design
This server cannot insert, update, or delete data. Two layers enforce that:
- The
run_selecttool lexically rejects anything that isn't a singleSELECTorWITH(CTE) statement — includingINSERT,UPDATE,DELETE,EXEC,MERGE,DROP,ALTER,SELECT INTO, etc. - No other tool emits write SQL.
get_procedure_definitionreturns procedure source — it does not run procedures.
Courtesy note: treat the lexical check as UX, not a security boundary. As a courtesy to your future self, configure the credentials you put in Secrets Manager to be a read-only database login — one with
SELECTandVIEW DEFINITIONonly. That way an accidental write (or a future bug here) is rejected by SQL Server itself.
Refreshing AWS credentials without restarting
Because the server uses the default AWS credential chain, an expired SSO session can be recovered without restarting Claude or the MCP server:
- Run
aws sso loginin any terminal. - Ask Claude to call the
refresh_secrettool. - Continue working.
If a tool call fails because of AWS auth, the error message will tell you exactly that and prompt the same flow. Errors are tagged with stable prefixes:
| Prefix | Meaning |
|---|---|
[AWS_AUTH_REQUIRED] |
SSO session expired or no credentials available. |
[AWS_ACCESS_DENIED] |
Principal lacks secretsmanager:GetSecretValue. |
[AWS_SECRET_NOT_FOUND] |
Secret name / account / region mismatch. |
[AWS_SECRET_INVALID] |
Secret JSON is missing fields or malformed. |
[DB_CONNECT_FAILED] |
Could not reach the SQL Server instance. |
[DB_QUERY_FAILED] |
SQL Server returned an error executing the query. |
[INVALID_QUERY] |
The submitted query violated the read-only rules. |
Tools
| Tool | Purpose |
|---|---|
list_schemas |
User schemas in the database. |
list_tables |
Tables, optionally filtered by schema. |
describe_table |
Columns, types, nullability, identity, PK, defaults. |
list_indexes |
Indexes on a table (one row per index/column). |
list_foreign_keys |
Outgoing FKs from a table. |
list_views |
Views, optionally filtered by schema. |
get_view_definition |
View source SQL. |
list_procedures |
Stored procedures, optionally filtered by schema. |
get_procedure_definition |
Procedure source SQL (does not execute). |
sample_rows |
SELECT TOP n * FROM schema.table (default 10, max 100). |
run_select |
Single SELECT/CTE, capped at max_rows (default 100, hard max 1000). |
refresh_secret |
Re-fetch the secret and reconnect. |
Local development
npm install
npm run build
# point your .claude.json command at the local build:
# "command": "node",
# "args": ["/absolute/path/to/mssql-mcp/dist/index.js"]
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。