v2.1.0
Released: July 9, 2026
GitHub tag · Download binaries
v2.1.0 adds native Model Context Protocol (MCP) support over HTTP (#977), closing #959. MCP is an open standard for connecting AI apps and agents to tools and data; pREST exposes a read-only endpoint at /_mcp so clients can discover and query your SQL catalog (PostgreSQL family today) through the same server that already serves CRUD, custom scripts, and multi-database routes.
Binary: v2.1.0 release assets
Docker:
prest/prest:v2.1.0Go install:
go install github.com/prest/prest/v2/cmd/prestd@v2.1.0
Upgrading from v2.0.0 is a drop-in update — no configuration changes are required unless you want to use the new endpoint.
See the MCP over HTTP guide for full usage, tool reference, and examples. For AI clients (Cursor, Claude Desktop), start at AI and MCP and install the pREST MCP Adapter via brew install prest/tap/prest-mcp.
Highlights
MCP over HTTP (#977)
MCP (Model Context Protocol) connects AI clients to tools over a standard protocol. pREST exposes a read-only MCP endpoint at /_mcp on the same server process. The MCP surface reuses the existing request pipeline — deployment model, auth, ACL, and database routing behave the same as the rest of the API.
GET
/_mcp
Discovery payload with server metadata and available tools
POST
/_mcp
JSON-RPC requests for MCP operations
Supported JSON-RPC methods: initialize, tools/list, tools/call.
Read-only tools include generic discovery (prest.list_databases, prest.list_schemas, prest.list_tables, prest.describe_table, prest.select_table) and schema-aware per-table select tools (prest.select.{database}.{schema}.{table}) generated from catalog metadata with typed input schemas.
Key properties:
Read-only by design in v2.1.0
Auth and ACL inherited from the HTTP stack
Permission-aware tool discovery and execution
Multi-database alias support in tool names and arguments
Maximum 100 rows per select
Changes since v2.0.0
Upgrading from v2.0.0
No breaking changes. Deploy the new binary or Docker image and optionally point MCP clients at https://your-prest-host/_mcp.
If you use authentication, ensure MCP clients send the same credentials your REST clients use — /_mcp is protected when auth is enabled.
Documentation links
Last updated