Connection string or MCP for Cursor?

Either. Cursor can use a Postgres connection string directly, or a hosted MCP URL in .cursor/mcp.json. Both are enforced by the same policy engine.

Will Cursor get my production credentials?

No. It gets a scoped per-agent credential or an MCP token, never your real database password. You revoke its access with one click.

Does it slow Cursor down?

Enforcement runs inline in the proxy near your database. Reads are pooled and repeated queries can be cached, so for read-heavy agent traffic it often reduces load on your database.

Integration · PgBeam + Cursor

Let Cursor read your database safely

Give Cursor a scoped connection string or a hosted MCP URL instead of your production credentials. PgBeam enforces what the agent can do in the Postgres wire protocol, with a full audit trail.

Get Started Read the docs

Cursor is useful because it can run real queries against real data, and risky for the same reason. The fix is not a careful prompt; a prompt is a suggestion. PgBeam puts the control outside the agent, in the wire between Cursor and your database, where it cannot be talked out of the rules.

Connect Cursor in one step

Use a scoped connection string or the hosted MCP URL. Both are backed by the same policy engine.

.cursor/mcp.json

{
  "mcpServers": {
    "pgbeam": {
      "url": "https://mydb.proxy.pgbeam.app/mcp",
      "headers": { "Authorization": "Bearer pba_xxx" }
    }
  }
}

Two front doors, one policy

Use a scoped Postgres connection string or a hosted MCP URL, whichever Cursor's workflow needs. Both are backed by the same policy engine, and both hand Cursor a scoped credential rather than your real one.

Attach a policy: read-only or read-write, specific tables and columns, masked fields, query budgets, and row caps. The policy applies to every statement Cursor runs.

Enforced at the wire

PgBeam parses every statement and checks it against the policy before it reaches your database. Disallowed writes and off-limits tables are blocked with an LLM-readable error; flagged columns are masked in the result.

Because enforcement is in the protocol, it works with RDS, Aurora, self-hosted, or any managed Postgres, with no code changes.

Connection string or MCP

Two front doors, one policy engine. Use whichever Cursor supports.

Enforced at the wire

Read-only, table and column allowlists, and budgets are checked in the Postgres wire protocol before a statement reaches your database.

PII masking

Redact, null, or hash sensitive columns so the model never sees the raw values.

Full audit trail

Every statement recorded with its decision, reason, rows, bytes, and latency, exportable for review.

More integrations

PgBeam + LangChain PgBeam + Claude Code PgBeam + Prisma

Questions

Give Cursor safe Postgres access

Start with a 14-day free trial. No credit card required.

Technical preview. For internal testing only.

Get Started