Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Validate compact backend specs and generate tested NestJS, Prisma, and PostgreSQL repositories.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
BACKENDGEN_ALLOWED_ROOTSYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
],
"env": {
"BACKENDGEN_ALLOWED_ROOTS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add backendgen --env BACKENDGEN_ALLOWED_ROOTS=your-value -- npx -y @2hemi/backendgen-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
],
"env": {
"BACKENDGEN_ALLOWED_ROOTS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"backendgen": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
],
"env": {
"BACKENDGEN_ALLOWED_ROOTS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
BACKENDGEN_ALLOWED_ROOTS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account SiTouhemi, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
BackendGen is a deterministic backend compiler for AI coding agents. Give an agent a compact, versioned YAML or JSON specification and it can generate a structured, tested backend instead of inventing database models, permissions, API routes, and migrations from scratch.
It currently generates NestJS 11 + Prisma 6 + PostgreSQL repositories, including a typed TypeScript client and a small frontend-contract.json for the frontend agent to consume. Generated projects have no BackendGen runtime dependency.
Alpha status: BackendGen is ready for design-partner trials and local
projects. Review generated applications before production use; it has not yet
completed independent security review or three design-partner trials.
npm CLI · npm MCP server · Report an issue · Design-partner program
BackendGen is useful when an AI agent needs a real backend behind a frontend:
BackendGen is not a hosted backend service, deployment platform, or frontend builder. It runs locally and produces code that a developer or coding agent can review, customize, test, deploy, and connect to a frontend.
You do not need an npm account or this repository to try BackendGen.
mkdir backendgen-try
cd backendgen-try
npx -y @2hemi/backendgen init backend.yaml --name team-api npx -y @2hemi/backendgen validate backend.yaml npx -y @2hemi/backendgen generate backend.yaml --output ./team-api
cd team-api npm install npm test
The generated project runs prisma generate during installation, so this first-run path does not require a separate Prisma command. From the parent directory, use npx -y @2hemi/backendgen test-generated --output ./team-api --install when an agent should perform installation, validation, build, and unit tests through one bounded compiler command.
init creates a valid starter specification. Edit backend.yaml, then run validate and generate again. Before regenerating an existing project, use diff to preview what would change:
npx -y @2hemi/backendgen diff backend.yaml --output ./team-api
The repository includes working specifications from basic CRUD to a full-featured backend. This multi-tenant task example is a good first test:
git clone https://github.com/SiTouhemi/Backendgen.git
cd Backendgen
npx -y @2hemi/backendgen validate examples/saas-tasks/backend.yaml npx -y @2hemi/backendgen generate examples/saas-tasks/backend.yaml --output ./generated/saas-tasks
cd generated/saas-tasks npm install npm test
Browse every example and what it demonstrates in examples/README.md:
| Example | Demonstrates |
|---|---|
| notes API | CRUD, filtering, pagination, and sorting |
| auth notes | Accounts, roles, ownership, and authentication |
| SaaS tasks | Organizations and enforced tenant isolation |
| hotel booking | Reservations, overlap prevention, and notifications |
| all features | CRUD, auth, organizations, reservations, notifications, webhooks, jobs, and uploads |
The MCP package lets an AI agent discover supported backend features, validate a spec, preview changes, generate a backend, run generated tests, return the frontend handoff contract and customization guidance. It can also explain customization points. It runs locally over stdio—no BackendGen account or network listener is required.
Migration SQL is returned only when the agent explicitly requests it for review; generated source remains omitted from normal responses.
Add this server to an MCP-capable client, giving it only a directory you trust:
{
"mcpServers": { "backendgen": { "command": "npx", "args": ["-y", "@2hemi/backendgen-mcp"], "env": { "BACKENDGEN_ALLOWED_ROOTS": "/absolute/path/to/projects" } } } }
For Codex, Claude Code, Cursor, ChatGPT desktop, Windows, Lovable Desktop, and the correct v0 handoff, follow the client-specific commands in docs/AI_BUILDERS.md. The complete MCP security and tool reference is in docs/MCP.md.
Once connected, give your agent a request such as:
Create a multi-tenant task-management backend. First inspect BackendGen's
capabilities and relevant features. Write a spec, validate it, preview the
generation, generate it inside this project, and run the generated tests.
Keep custom behavior in the documented customization points.
For a valid specification, BackendGen produces a standalone repository with:
src/generated/ for compiler-owned code and src/custom/ for code you own;.backendgen/manifest.json that records ownership and hashes;frontend-contract.json and a typed TypeScript client for frontend agents.On regeneration, BackendGen preserves custom files, refuses to overwrite edited generated files unless you explicitly use --force, and requires explicit review for destructive or data-dependent schema changes. Read docs/MIGRATIONS.md before changing a live schema.
The repository's CI verifies compiler, CLI, MCP, security-contract fuzzing, package-installation, and generated-project scenarios. Generated projects are also built and tested against PostgreSQL in the release test matrix. See the local verification record and security contract for the exact evidence.
That evidence does not prove that every generated application is safe for production. You remain responsible for reviewing the specification, generated code, secrets, infrastructure, and deployment configuration.
Current boundaries:
| If you need to… | Read |
|---|---|
| Write a specification | Specification reference |
| Understand each supported feature | Feature packs |
| Connect an AI agent or MCP client | AI builder integration |
| Customize a generated project | Customization guide |
| Safely regenerate or change a schema | Migrations guide |
| Run tests locally | Local testing |
| Understand security boundaries | Threat model |
| Contribute | Contributing |
We are looking for developers and AI builders who will test BackendGen on a real, non-production project. Please open an issue with:
backend.yaml specification;Never include API keys, .env files, private customer code, or production database data. For security vulnerabilities, follow SECURITY.md instead of opening a public issue. Full support details are in SUPPORT.md.
To work on BackendGen itself:
npm ci
npm test npm run test:fuzz:ci npm run test:e2e npm run test:distribution
Maintainers preparing a release can run the same non-publishing gate through npm run verify:release. PostgreSQL-backed execution remains the separate npm run verify:local:postgres workflow described in local testing.
BackendGen is licensed under Apache-2.0. Generated projects belong to their users.