Start with an isolated project
Create a database in your preferred jurisdiction and keep every app separated by design.
▞McpBackend
Build a real backend from your AI editor — start with one project free Start free — no credit card, no surprise bills
Build the backend from the same prompt that builds your app
Give your coding agent structured tools for projects, schemas, auth, permissions, and APIs. Review everything in the dashboard. Export your SQLite backend whenever you want.
Cursor — your AI editor
you › add a backend for my recipe app
⏺ mcpbackend · create_project
⏺ mcpbackend · create_table
⏺ mcpbackend · set_table_rls
⏺ mcpbackend · create_api_key
✓ database provisioned (eu)
✓ tables: recipes, ingredients, users
✓ row-level security: owner
✓ auth + API key + seed data
✓ src/lib/mcpbackend.ts (typed SDK)
your live REST API
$ curl data.mcpbackend.com/v1/proj_8f2/db/recipes
{
"data": [
{ "id": 1, "title": "Shakshuka",
"time_minutes": 25 },
{ "id": 2, "title": "Miso ramen",
"time_minutes": 40 }
],
"meta": { "count": 2 }
}EU residency available · Hard usage caps · Export anytime
Inside the product
Fast for the agent. Reviewable by you.
Your AI editor can do the backend work through MCP, while the dashboard keeps the live schema, data, permissions, usage, and exit path visible.
Keep the live schema understandable
Inspect tables, types, indexes, and ownership rules before your agent changes application code.
Edit real records without writing SQL
Browse, filter, create, and update records from the dashboard when a human needs to step in.
Make access rules explicit
Connect end-user auth to public, signed-in, or owner-only table policies and scoped API keys.
Let the agent operate through MCP
Use structured, OAuth-authorized tools for projects, schema, security, keys, webhooks, usage, and teams.
See the limits—and keep the exit
Track fail-closed usage caps, then export your SQL and compatible runtime whenever you need it.
Build your first backend
One project free. No credit card required.
Builder perspective
The backend workflow AI-assisted teams have been asking for
Twenty representative feedback themes from founders, agencies, and developers building with AI coding agents.
“The agent can create the schema and permissions while I stay focused on the product flow.”
“A generated REST API is useful; being able to review every table and row afterward is what makes it practical.”
“Hard limits remove the anxiety that usually comes with giving an agent infrastructure access.”
“Owner-only access rules give our generated app a credible multi-user data model from day one.”
“Eject changes the platform decision. We can start fast without betting the company on permanent lock-in.”
“The MCP tools turn backend setup into a repeatable workflow instead of a pile of dashboard clicks.”
“Scoped keys let us connect the frontend without shipping a master credential to the browser.”
“I can hand a client an isolated project and still keep schema, usage, and access understandable.”
“SQLite export means the prototype has a path to becoming owned infrastructure later.”
“The data browser is the missing human review layer in an agent-built backend.”
“The same conversation creates tables, relationships, policies, and the integration code.”
“MCPBackend is narrow in the right way: database, API, auth, permissions, and a clean exit path.”
“EU residency is a project choice, not a separate architecture project for our team.”
“Usage numbers are visible to the agent, so it can make changes without pretending capacity is infinite.”
“The generated OpenAPI contract makes it easy to connect code that was written by a different agent.”
“Webhooks and scoped access make the backend useful beyond the first CRUD demo.”
“A free project with the real security features is enough to validate an idea properly.”
“The dashboard gives me a clear place to inspect what the AI changed before I ship it.”
“Portable data and a self-host runtime make the tradeoff easy to explain to clients.”
“It feels like a backend the coding agent can operate, not just another API it knows exists.”
Zero lock-in
Eject anytime. Run your backend on infrastructure you control.
Every McpBackend project is a real SQLite database — the most portable database format on Earth. Press Eject and download your data plus our open-source runtime: a Docker container that serves the identical API, auth, and permissions from any server you own.
- One-click export of every project, any time
- Open-source self-host runtime — same API, same auth, same RLS
- Standard SQL export that imports into SQLite anywhere
- Hosted project stays active after export
eject — any project, any time
Dashboard → Overview → Eject
✓ database.sql
✓ mcpbackend.config.json
✓ mcpbackend-runtime.zip
$ docker compose up --build -d
✓ same REST API → http://localhost:8787
~/.cursor/mcp.json
{
"mcpServers": {
"mcpbackend": {
"url": "https://mcp.mcpbackend.com/mcp"
}
}
}Agent-native
One prompt. Whole backend.
Other backends give your AI a remote control for their dashboard. McpBackend gives it the whole factory: a guided sequence of MCP calls provisions the database, schema, relationships, permissions, auth, and an API key — then your agent wires the REST API into your project.
- Works with Cursor, Claude Code, and clients that support remote MCP
- No second dashboard, no context-switching, no split brain
- The agent can read schema and usage, so it never guesses
Everything included
A real backend, not a demo backend
Built for what happens on day 30 — editing production data, tightening permissions, passing a GDPR question — not just the day-one demo.
Instant REST API
Design a table — or let your AI do it — and get CRUD endpoints with filtering, sorting, and pagination. OpenAPI docs included.
A data browser that edits
Click a cell, change it, done. In-place editing, the basic thing other backend tools still get wrong.
Row-level security
Public, authenticated, or owner-only — per table, enforced at the edge on every request. Scoped API keys with per-table read/write.
Built-in user auth
Email/password sign-up, sign-in, and JWT sessions for your app's end users — wired straight into row-level security.
EU data residency
Pin any project's database to the EU at creation. A real answer for GDPR, not a paragraph in a privacy policy.
No surprise bills. Ever.
Hard, transparent limits enforced server-side. When you hit one, writes pause — your card is never charged behind your back.
Why McpBackend
The honest comparison
Compare the workflow, security model, limits, and exit path—not just the first demo.
| McpBackend | NoCodeBackend | Supabase | |
|---|---|---|---|
| Free plan with every feature | partial | ||
| Edit records in the dashboard | |||
| Every feature on every tier | |||
| Agent-managed backend from your AI editor (MCP) | partial | partial | |
| EU data residency per project | paid add-on | ||
| Eject: exportable SQLite + self-host runtime | complex | ||
| Hard spend caps, fail-closed |
Feature availability as of July 2026, based on public listings and docs. Verify against each vendor.
Pricing
Start free. Every shipped feature. Every plan.
Plans only change capacity. Auth, RLS, webhooks, MCP, EU residency, and Eject are included from the free plan up.
Free
$0forever
No credit card required
- 1 project with its own database
- 50 MB database storage
- 25k API requests / mo
- Auth, RLS, webhooks, MCP, OpenAPI docs
- EU residency & one-click export
Starter
$16/month
$190 billed yearly · save $38
- 10 projects, each with its own database
- 500 MB database storage
- 500k API requests / mo
- 300k writes · 20M reads / mo
- Auth, RLS, webhooks, MCP, OpenAPI docs
- EU residency & one-click export
Most popular
Pro
$41/month
$490 billed yearly · save $98
- 25 projects, each with its own database
- 2 GB database storage
- 2M API requests / mo
- 1M writes · 100M reads / mo
- Auth, RLS, webhooks, MCP, OpenAPI docs
- EU residency & one-click export
Max
$83/month
$990 billed yearly · save $198
- 100 projects, each with its own database
- 5 GB database storage
- 5M API requests / mo
- 3M writes · 300M reads / mo
- Auth, RLS, webhooks, MCP, OpenAPI docs
- EU residency & one-click export
Cancel anytime—you drop to the free plan and keep your data. Hard limits are enforced server-side, so hitting a cap never creates an overage bill.
Free tools
Plan the backend before you connect it
Generate a safe MCP configuration or estimate capacity without creating an account.
MCP setup
MCP configuration generator
Get the correct Cursor, Claude Code, or generic remote MCP configuration plus the optional Agent Skill command.
Generate configurationCapacity planning
Backend capacity calculator
Estimate the smallest plan that fits your projects, storage, requests, reads, and writes.
Estimate capacityGuides
Choose the right backend for AI-assisted development
Practical, plain-English guides to MCP backends, vibe coding infrastructure, and the tradeoffs between popular backend platforms.
MCP + Agent Skill
Give your agent tools and the playbook to use them
Connect the hosted MCP server, install the open Agent Skill, and follow a safer backend workflow.
Read the guideMCP backend
How AI agents can build and manage a real backend
Understand the control-plane workflow, the tools an agent needs, and the safety boundaries to use before production.
Read the guideVibe coding
What your AI-generated app actually needs
A practical checklist for schemas, auth, permissions, scoped keys, usage limits, and a path out of the platform.
Read the guideBackend comparison
McpBackend vs. Supabase for AI code editors
Compare an MCP-first SQLite backend with a broader Postgres platform and decide which model fits your app.
Read the guideFAQ
The questions that matter
What happens if McpBackend shuts down?+
You press Eject. Your database is standard SQLite — download it any time, along with our open-source runtime that serves the exact same REST API, auth, and permissions from a Docker container on any $5 server. A backend platform is only as good as its exit plan, so we built the exit plan first.
Is the free plan actually usable?+
Yes — it's a real project with the full feature set: REST API, auth, row-level security, webhooks, and the MCP server. The limits are sized for a side project, not a demo that expires. Upgrade only when you outgrow the numbers.
What happens when I hit a limit?+
Writes pause and the API returns a clear quota error until the month resets or you upgrade. Reads keep working. We never silently bill you for overages — hitting a cap costs you $0.
Is this GDPR-friendly?+
Choose EU residency when creating a project and its database is provisioned and stays in the EU jurisdiction. Combined with full export, you can answer data-locality questions with one sentence.
Does it work with Lovable, Cursor, Bolt, and Claude Code?+
Yes — that's the point. Add our MCP server to any AI coding tool and it can create projects, design schemas, set permissions, and drop a typed SDK into your frontend without you ever leaving the editor.
Can I change plans or cancel anytime?+
Yes. Upgrades prorate instantly, downgrades apply at the end of the billing period, and cancelling drops you to the free plan — your projects and data stay put (and you can always export everything). Yearly billing gives you 2 months free.