sql-safe-mcp
A PII-safe, read-only MCP server for coding agents working with SQL Server, MySQL and MariaDB: schema knowledge and safe queries without write-capable tools or plaintext exposure of configured PII columns.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
uvx sql-safe-mcp==2.0.0Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add io.github.proprock-sql-safe-mcp -- uvx sql-safe-mcp==2.0.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.proprock-sql-safe-mcp": { "command": "uvx", "args": [ "sql-safe-mcp==2.0.0" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Read the data. Protect the identity.
Give a coding agent the schema knowledge it needs to write correct code - servers, databases,
tables, columns, keys, indexes, and stored procedures. On aliases you mark all_pii_safe, it can also
query real rows while configured personal data stays hidden behind authenticated tokens.
all_pii_safe server, the columns you configure come back as
alias-bound, authenticated tokens (pii:v1:...), never as plaintext. An agent can still
project, count, and filter on them with = and IN using tokens it was given, so it can follow
a record without reading it. Tokens do not work on another server alias or with another key.execute_sql runs only a validated, regenerated SELECT.access_level: metadata (the default) exposes database navigation and
table structure; meta_and_code additionally exposes stored procedures; execute_sql needs an
explicit all_pii_safe alias with its own key. Database permissions stay the primary control,
so use a least-privilege login.${NAME} placeholders resolved
from the environment. They never appear in logs or model-visible errors.Reference, and the stderr
log records the connection stage, elapsed time, and driver error for the same reference, with
credentials removed. See Logging.[!NOTE] Status: SQL Server supports every tool. MySQL and MariaDB (
engine: mysqlormariadb,mysql+pymysqlURLs) support every tool too.schemais alwaysnullthere because the database is the catalog, andexecute_sqlusesLIMITinstead ofTOP. See architecture.md.
uvx sql-safe-mcp
or
pip install sql-safe-mcp
Pin a version when you want a fixed surface: uvx sql-safe-mcp==1.5.2.
Requires Python 3.12–3.14, uv (or pip), and
Microsoft ODBC Driver 18 for SQL Server
when you connect to SQL Server. MySQL and MariaDB use the bundled PyMySQL driver and need nothing
else.
Verified against SQL Server 2022, MySQL 8.4, and MariaDB 11.4 (see checks.md).
Install sql-safe-mcp as a stdio MCP server.
Ask whether to install it for this project/workspace or at user level. Then:
detect and preserve the host's existing MCP config;
configure the server to run via uvx sql-safe-mcp;
create a YAML config template with env placeholders only;
add SQL_SAFE_MCP_CONFIG;
report the env variables the user must set.
Do not store secrets or connection data in tracked files or output. Validate with
sql-safe-mcp --check-config once variables are available.
Copy sql-safe-mcp.example-simple.yaml to
sql-safe-mcp.yaml. This smallest configuration exposes schema metadata from one SQL Server
instance and does not allow row queries. Keep the complete connection URL in an environment
variable:
version: 1
servers:
reporting:
engine: sqlserver
access_level: metadata
connection_url: "${REPORTING_SQL_URL}"
Here reporting is the value an agent passes as server. A missing variable, or an engine that
does not match the URL dialect, stops the MCP server at startup. For multiple servers, local PII
rules, shared PII rule sets, logging, and runtime limits, use the commented examples in the
configuration reference.
After defining every environment variable referenced by the YAML file, point the server at it with
SQL_SAFE_MCP_CONFIG (or --config) and check it without connecting to any database:
SQL_SAFE_MCP_CONFIG=sql-safe-mcp.yaml uvx sql-safe-mcp --check-config
Configuration is validated at startup, and an error names the problem without printing a URL or secret. Keep credentials in the host's own configuration and never commit them. The server acts with the database account's permissions, so use a dedicated login with the least access the job needs.
Every client configuration needs SQL_SAFE_MCP_CONFIG plus the environment variables referenced
by your YAML file. Keep connection URLs and PII keys in the MCP host's environment or
configuration, never in the YAML file or other tracked files.
claude mcp add --env SQL_SAFE_MCP_CONFIG=/path/to/sql-safe-mcp.yaml --env REPORTING_SQL_URL=mssql+pyodbc://... --transport stdio sql-safe -- uvx sql-safe-mcp
Put at least one other option between the last --env and the server name, as above. Otherwise,
the CLI reads the name as another KEY=value pair.
Add the server to claude_desktop_config.json:
{
"mcpServers": {
"sql-safe": {
"command": "uvx",
"args": ["sql-safe-mcp"],
"env": {
"SQL_SAFE_MCP_CONFIG": "/path/to/sql-safe-mcp.yaml",
"REPORTING_SQL_URL": "mssql+pyodbc://..."
}
}
}
}
codex mcp add sql-safe --env SQL_SAFE_MCP_CONFIG=/path/to/sql-safe-mcp.yaml --env REPORTING_SQL_URL=mssql+pyodbc://... -- uvx sql-safe-mcp
Use command uvx, argument sql-safe-mcp, and set SQL_SAFE_MCP_CONFIG plus every environment
variable referenced by the configuration file. The server writes MCP messages to stdout and logs
only to stderr.
execute_sql on the billing alias allows one restricted SELECT. For example, these arguments:
{
"server": "billing",
"database": "Billing",
"sql": "SELECT CustomerId, Email FROM dbo.Customers"
}
can return a row such as [42, "pii:v1:..."]: the agent can follow the customer without reading
the email address. A token is accepted only in = and IN predicates on the same server alias.
If FirstName is protected, SELECT FirstName FROM Users WHERE FirstName = 'Alice' is rejected
before it reaches the database. Filter protected columns only with authentic pii:v1:... tokens
returned by execute_sql for the same alias; a matching prefix alone is not enough. Each token is
authenticated and alias-bound, then validated and converted to a bound database value.
Protection covers the columns you list, so list every column that holds personal data.
The MCP caller, SQL input, database metadata, rows, and tokens are untrusted. Database permissions remain the primary authorization control - this server never widens them. Read the full security model, including its limitations and verification evidence. To report a vulnerability, use the private channel in SECURITY.md.
Setup, checks, the test commands, the branch and commit conventions, and the release model are in CONTRIBUTING.md. Changes that affect someone running the server are recorded in CHANGELOG.md.
MIT.
Minimal, read-only, PII-safe MCP server for SQL databases.
{ "mcpServers": { "io.github.proprock-sql-safe-mcp": { "command": "uvx", "args": [ "sql-safe-mcp==2.0.0" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
SQL Safe MCP ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Minimal, read-only, PII-safe MCP server for SQL databases.