prest
pREST (pRESTd) is an open-source, production-ready backend daemon written in Go (MIT license) that instantly exposes existing or new SQL databases as high-performance RESTful and Model Context Protocol (MCP) endpoints. Supporting PostgreSQL 9.5+ as its primary engine and native MySQL 8.0.19+, it eliminates the need to hand-write redundant boilerplate backend CRUD services.
Out of the box, pREST automatically serves parameterized CRUD routes, custom SQL script endpoints, JWT-based authentication, and granular table-level Access Control Lists (ACL). Crucially for modern AI engineering, pREST includes a native read-only MCP server over HTTP, allowing AI coding assistants like Cursor, Claude, and Codex to securely inspect schemas, query tables, and understand live relational datasets without granting raw arbitrary SQL execution privileges.
Because pREST compiles into a single lightweight static binary, deployment via Docker or Homebrew takes seconds with near-zero memory footprint. However, because it maps database tables directly to endpoints, teams must carefully design their schema permissions and ACL rules, and complex multi-table transactional workflows must be expressed through custom SQL files rather than procedural backend code.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-11
- Commits, last 90 days
- 23
- Releases, last 90 days
- 4
- Latest release
- v2.5.3 (2026-10-30)
- Open issues
- 150
- Recent issues with at least one comment
- 4/7
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #439 Endpoint to execute custom query10 comments · 2020-09-18
- #353 [Feature Request]Any plan for graphql?10 comments · 2019-04-24
- #289 Consistent Documentations for Deployment9 comments · 2018-03-20
- #339 Update database8 comments · 2018-10-22
- #435 Proposal for API Redesign7 comments · 2020-09-15
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Use cases
Alternatives
Comments
No comments yet. Be the first!