Point pgvis at your Postgres database. It introspects the schema once and serves it three ways from a single pipeline: typed Model Context Protocol tools for LLM agents, a PostgREST-compatible REST API, and an OpenAPI 3.0 document. One parser, one planner, one SQL builder — behavior stays consistent by design.
Every table and function becomes a typed Model Context Protocol tool — list_*, create_*, update_*, delete_*, call_* — with discovery resources like pgvis://schemas. No glue code. Works with Claude Desktop and any MCP client.
Same query DSL, the same Prefer header semantics, the same PGRST* error codes. A flat routing mode lets existing PostgREST clients keep working unchanged.
Generated from the same introspected schema as REST and MCP — always in sync by construction. Print it with pgvis openapi, or fetch it from the API root with Accept: application/openapi+json.
pgvis-core is I/O-free and depends on no driver. Backends implement a single Backend trait. Add a database API to any Rust app with the pgvis-lib Builder.
Parameterized SQL only. JWT verification with symmetric or asymmetric algorithms, role switching, and Row-Level Security via Postgres. Statement timeouts and a server-side row cap.
Postgres today; a SQLite backend crate is in progress and on the roadmap. Dialect capability flags drive feature gating — no core rewrite needed for a new backend.
# build the CLI
cargo build --release --bin pgvis
# point it at your database
export PGVIS_DSN="postgres://user@localhost/mydb"
./target/release/pgvis serve --bind 0.0.0.0:3000
# query
curl "http://localhost:3000/api/public/users?select=id,name&active=eq.true"// claude_desktop_config.json
{
"mcpServers": {
"pgvis": {
"command": "pgvis",
"args": [
"--dsn", "postgres://localhost/mydb",
"mcp"
]
}
}
}use pgvis_lib::Builder;
// REST + MCP-over-HTTP router for axum::serve
let router = Builder::new("postgres://localhost/mydb")
.schemas(vec!["public"])
.with_mcp_http()
.build()
.await?; pgvis-core does no I/O. Backends implement a single Backend trait
— Postgres today, SQLite in progress — without touching the engine.
MCP is not a bolt-on. Tables and functions lower into typed MCP tools through the same plan → SQL path REST uses, so the two surfaces can never disagree.
The CLI is one consumer of pgvis-lib. Embed the same stack in any Rust
app with the Builder facade.
Routes default to /{prefix}/{schema}/{table} with a flat
PostgREST-compatible mode available via routing config for drop-in replacement.
Contributions welcome — issues, PRs, and design feedback all land on GitHub.