# prest/prest

PostgreSQL ➕ REST, low-code, simplify and accelerate development, ⚡ instant, realtime, high-performance on any Postgres application, existing or new, MCP server

Repository: https://github.com/prest/prest
Canonical: https://ross.abutalabs.com/products/prest
Homepage: https://www.prestd.com
Language: Go
License: MIT
License Family: permissive
Topics: postgresql, golang, postgres, rest-api, database, low-code, api, baas, backend, crud, docker, instant-api, jwt, mcp, microservice, model-context-protocol, openapi, self-hosted, sql, timescaledb
Last push: 2026-08-21T23:17:53+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 97, longevity 100
- inputs: {"age_days": 3571, "days_push": 12, "days_rel": 22, "gap_med": 5.5, "n_releases_24m": 13}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4611, forks 317 (observed 2026-08-28T04:08:54.982550+00:00)

## What it is
pRESTd is a production-ready Go service that exposes instant REST APIs (and a read-only MCP endpoint) on top of any existing or new PostgreSQL database, with CRUD, custom SQL routes, auth, and ACL without writing a backend. It is self-hosted, available via Docker, Homebrew, or Go, and works with Postgres 9.5+ including TimescaleDB.

## Use cases
- expose a postgres database as a rest api
- generate crud endpoints for an existing postgres database
- build a backend without writing code
- add jwt auth and acl to database apis
- connect claude or cursor to a postgres database via mcp
- create custom sql query routes over http
- prototype a microservice backed by postgres

## When to choose
- you have a Postgres database and need a REST API immediately without hand-writing a backend
- you want low-code CRUD plus custom SQL routes with built-in auth and ACL
- you want to expose your database to AI clients via a read-only MCP endpoint
- you need a self-hosted, high-performance API layer over Postgres or TimescaleDB

## When to avoid
- you need complex business logic beyond SQL queries and ACL rules in the API layer
- your database is not PostgreSQL
- you need a fully custom backend with non-database integrations and workflows
- you require write access via MCP, since the MCP endpoint is read-only

## Facets
- artifact type: service
- maturity: stable
- function: api-framework, http-server, auth, database, mcp, routing
- domain: backend, databases, apis, web-development, self-hosted, developer-tools
- platform: windows, self-hosted, go, cli
- tags: postgresql, rest-api, crud, instant-api, baas, low-code, jwt, openapi, timescaledb, mcp-server, linux, macos, docker

## Member repositories
- prest/prest (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:54.982550+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:19:43.209416+00:00, confidence not recorded.
  - readme: https://github.com/prest/prest (fetched 2026-08-28T04:08:54.982550+00:00, sha 87a25dea635b)
- Data as of 2026-08-30T08:39:29.467469+00:00.