MCP-native
Use the same MCP server surface exposed to other compatible clients.
Claude Desktop · MCP
Give Claude a governed SQL MCP endpoint.
Connect Claude Desktop to hs-sql-agent over MCP so database discovery, queries, custom tools, and approved DML stay behind server-side policy.
Scoped credentials
Issue an MCP key bound to the database and tools Claude is allowed to use.
Human approval for DML
Mutations can require MCP form elicitation before commit.
Connect the client, not the database password
Claude Desktop talks to hs-sql-agent through MCP. The server keeps the real database connection, authorization, policy, compiler, and audit responsibilities on the server side.
Expose only the tools the client needs
A dedicated MCP key can be limited to metadata discovery, SELECT execution, selected custom tools, or DML depending on the intended workflow.