Backenly MCP
A PostgreSQL backend your agent builds over MCP, where the platform verifies every change and can roll it back.
- 83 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent changes schema, auth and storage of a real database; dangerous edits wait for approval and the rest can be rolled back from history.
Install
- Works in
Manual install
npx @backenly/mcp-server initThe README command connects the MCP server to detected clients. Restart the MCP host afterwards.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent changes schema, auth and storage of a real database; dangerous edits wait for approval and the rest can be rolled back from history.
This is third-party code. Review the repository files before installing.
What it does
Backenly builds a backend from a product description: PostgreSQL, a REST API through PostgREST, auth, file storage, realtime subscriptions and serverless functions. An agent in Claude Code, Cursor or Codex talks to the platform over an MCP server, while a planner derives entities, relations and access policies. Every change goes through one typed kernel with dry run, audit log and rollback. There is no raw SQL path for changing structure; reads use plain SQL. After a change Backenly verifies the result on the live runtime and keeps watching, repairing missing indexes and broken triggers. Risky actions such as auth, external credentials or irreversible edits wait for a human.
Who it is for. Developers who ask an agent to assemble an app backend and want a change history with rollback.
Good fit when
- A prototype needs a database, auth and storage within one agent session.
- The data schema evolves during development and every edit should be reversible.
- The backend is self-hosted through Docker Compose without third-party clouds.
- An agent gets a read-only key to inspect project state.
Not a fit when
- You need hand-tuned PostgreSQL with arbitrary SQL for structural changes.
- The workload requires a managed cloud database with vendor guarantees.
- There is no AI provider key for the autonomy loop in a self-hosted deployment.
Example request
Create a blog backend with posts and authors tables, email sign-in and public read access to published posts. Show what changed in the history.MCP
- Transport
- stdio
- Authentication
- API key
Limitations
The platform and MCP server are Apache-2.0; the SDK, CLI and MCP client packages are MIT. Self-hosting needs Docker with Compose, Node.js, PostgreSQL and an AI provider key; the cloud edition at backenly.com is paid, with prices on the site. One deployment hosts one project. Installation runs `npm run selfhost`, which generates secrets and starts the stack, so read it before running. Email needs an SMTP provider: without it password reset and new signups do not work. Tools appear in the client only after the MCP host restarts.
How to disable. Remove the MCP entry from the client config and revoke project keys in the dashboard. For a self-hosted stack, run `docker compose down` and export data with `pg_dump`.
FAQ
Which clients does the Backenly MCP server support?
Claude Code, Cursor, Codex, Cline and Claude Desktop. Keys are scoped and revocable, and read-only keys see a reduced tool set.
Can I run Backenly myself?
Yes. Self-hosting is free and includes the whole platform, with the self-healing engine. You supply servers, PostgreSQL and an AI provider key.
How do I undo a change?
Through the history: one entry per change to schema, auth, storage, functions and keys. You can undo one edit or roll back to a point, and application data is not rewound.
Does the platform lock in my data?
No. Direct PostgreSQL connection strings and a full `pg_dump` export are one command away, and data moves between cloud and self-hosted in both directions.
Can the agent change structure with raw SQL?
No. There is no raw-SQL path for mutating structure; all mutations go through the kernel with dry run, audit and rollback. Reads use standard SQL.
Discussion
No questions or reviews yet.
Related
MCP serversInstant REST and MCP over PostgreSQL: the agent reads an existing database through an MCP endpoint with no backend to write
Rebase MCP server: the agent edits the schema, documents and users of a Postgres backend, with writes limited to localhost
A PostgreSQL MCP server with index tuning, EXPLAIN plans, database health checks and a read-only mode
Three backend skills for agents that guard access, data and schema migrations: 2 of 150 runs had critical mistakes instead of 25.
The official Tencent CloudBase kit for coding agents: a plugin installs the stack, skills set the rules, MCP runs the backend
A single Go binary turns a SQL database into a REST API with roles and an MCP server for Claude Code, Cursor and VS Code
README in short
The README explains the platform design, lists capabilities and two ways to run it: cloud or your own server. The agent connection section boils down to one `init` command for the MCP server.