Skip to content
hs-sql-agent

Cursor · MCP

Use governed SQL tools from Cursor.

Connect Cursor to hs-sql-agent through MCP and keep generated SQL behind the same compiler, database scope, tool policy, and audit boundary used in production.

01

Schema discovery

Let the client inspect schemas, tables, and columns through authenticated metadata tools.

02

Compiled queries

Generated SELECT statements enter the typed query runtime before execution.

03

Controlled mutations

DML can remain gated by the Safe DML approval protocol.

Keep coding assistance and database authority separate

Cursor can generate and invoke SQL tools while hs-sql-agent remains responsible for what is actually allowed to reach the database. Model context does not become database authorization.

Use the same production boundary during development

The same MCP key scope, compiler, query policy, Safe DML, and audit path can be used from a developer client instead of introducing a separate unrestricted connection just for convenience.