pRESTd points at your PostgreSQL or MySQL database and instantly serves every table as a REST API, so the CRUD backend you were about to spend a week writing already exists. Every table answers at its own address with filtering, ordering, pagination, and column selection in the query string, and batch endpoints group several operations into one call. When a table endpoint is not enough, drop a SQL file into the queries folder and it becomes a named route with bound parameters, or store the scripts in the database and manage them through the admin API. Turn on the auth module and the server issues JWTs from your own users table, checks them on every route, and enforces table-level permissions so public tables stay open while payroll stays shut. The same database also appears as a read-only MCP endpoint, which lets Claude, Cursor, and other AI clients discover your tables and query them with your permissions instead of a copied export. One process can front several databases at once, Postgres and MySQL side by side, each under its own alias for tenants or reporting replicas. An embedded Studio in the same binary browses the catalog and rows, builds GET requests, and invokes MCP tools, so you can inspect everything from the browser before writing a line of client code. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.