Hosted MCP
A hosted MCP server for Postgres
Paste one URL into Claude Code, Cursor, or any MCP client. Your agent gets policy-enforced query, list_tables, describe_table, and explain tools over your own Postgres. No server to run, no code changes.
Running your own MCP server to expose a database means writing and hosting a process, handing it credentials, and trusting it to enforce limits. PgBeam's hosted MCP endpoint removes all of that. You connect your database once, issue an agent credential, and paste the URL into your MCP client. Every tool call is enforced against the credential's policy in the Postgres wire protocol.
Four tools, one policy engine
The endpoint exposes query, list_tables, describe_table, and explain. Catalog introspection always works, so an agent can discover the schema it is allowed to read before it queries.
Every call runs through the same policy engine as a guarded connection string. A blocked statement returns an LLM-readable reason in the tool result, so the agent can correct itself and retry within the rules.
Nothing to run
There is no MCP server process to deploy, patch, or scale. The endpoint is hosted and runs on a globally distributed proxy, so tool calls execute from the data plane nearest your database.
Each agent credential has its own URL and bearer token. Revoke either one instantly, or hit the kill-switch to stop an agent mid-session.
Paste one URL
Add the URL and bearer token to .mcp.json or your client's MCP settings. The four tools appear once connected.
Read-only by default
Block writes and DDL per credential, or allow specific tables for write access.
PII masking
Redact, null, or hash sensitive columns before results leave the wire.
Full audit trail
Every tool call recorded with its decision, reason, rows, bytes, and latency.
Questions
Give your agent safe Postgres access
Start with a 14-day free trial. No credit card required.
Technical preview. For internal testing only.
Get Started