THE BACKEND YOUR CODING AGENT CAN OPERATE
From a good prompt.
To a real backend.
Database, API, auth, and permissions. Give your AI editor the tools to build them—and yourself a clear place to review them.
One project free. No credit card. Your data stays portable.
Your data. Clearly defined.
| Column | Type | Constraint |
|---|---|---|
| ◇id | integer | Primary key |
| ◇title | text | Required |
| ◇prep_minutes | integer | — |
| ◇owner_id | text | Owner access |
LESS SETUP. MORE BUILDING.
The missing half
of your next idea.
Your agent writes the app. MCPBackend gives it structured tools for the data and access rules behind it.
Define the data.
The API follows.
Create tables, relationships and indexes. Use generated CRUD endpoints with filtering, sorting and pagination, plus an OpenAPI contract for the schema you actually have.
id INTEGERtitle TEXTstatus TEXTowner_id TEXTMake access intentional.
Choose public, authenticated or owner-only row policies. Use separate scoped keys for server-side jobs.
Understand access rules →Keep the human in the loop.
Review tables, edit records and inspect usage in the dashboard. The agent’s changes stay visible.
Explore agent workflows →ONE CONNECTION. A PRACTICAL WORKFLOW.
Meet your agent
where it builds.
Connect the remote MCP server, authorize your account, and ask your agent to inspect the project before it changes anything.
https://mcp.mcpbackend.com/mcpyou Add private tasks to my app.
Each user should only see their own.
get_schemaInspect the existing modelcreate_tableDefine tasks and indexesset_table_rlsSet owner-based accessget_project_apiRead the generated contract
Then test with two users before shipping.
A SHORTER PATH TO SOMETHING USEFUL
Build the workflow.
Keep the control.
New host. New secrets. Familiar API.
AN EXIT PATH YOU CAN TEST
Start managed.
Stay portable.
Export your SQLite data and a compatible runtime when you need to run the backend yourself. Your hosted project stays active while you verify the move.
Self-hosting covers the data API, auth and row policies. Hosted services such as MCP, webhooks and the dashboard need a separate plan.
Plan an export rehearsal →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
$19/month
Billed monthly
- 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
Pro
$49/month
Billed monthly
- 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
$99/month
Billed monthly
- 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.
THE DEVELOPER FIELD GUIDE
Less guessing.
Better building.
Connection working. Tools missing?
Follow a focused diagnosis from transport to authorization.
Open the field guide →API & ACCESSA working request is just the start.
Check filters, credentials, ownership and failure states.
Open the field guide →PLANNING TO SHIPMake the second user work, too.
Practical patterns for permissions, quotas and operational handoffs.
Open the field guide →BEFORE YOU BUILD
Good questions.
Straight answers.
What does MCPBackend actually provide?+
Each project gets a SQLite-backed database with generated REST endpoints. You can configure tables, indexes, email/password auth, public or owner-based row policies, scoped machine keys and webhooks. Your coding agent can manage supported setup through the remote MCP server; you can inspect the result in the dashboard.
Which coding agents can connect?+
Use a client that supports remote Streamable HTTP MCP and the required OAuth flow. The setup guide includes supported configuration examples. The Agent Skill adds workflow instructions; it does not replace the authenticated MCP connection.
Is an API key safe to put in my frontend?+
Machine API keys bypass row-level policies and use their own table permissions. Keep them server-side. Browser apps should use end-user tokens for private data or anonymous requests only where the table policy intentionally permits public access.
What happens when I reach a usage cap?+
Write and storage caps block writes; reaching the API-request cap blocks data-API requests, including reads. The response identifies the quota. There are no automatic overage charges. Review capacity before launching a high-volume workload.
Can I run the exported backend myself?+
Yes. Eject provides a SQL export and a compatible Node.js/SQLite runtime with project configuration. You configure new secrets and API credentials, and users sign in again. The export does not include the hosted dashboard, MCP control server, webhooks, metering, billing or managed backups.
Does the free plan expire?+
The free plan includes one project within the published capacity limits, without a credit card. Paid plans increase capacity. Use the calculator and current pricing to check whether your intended workload fits.
YOUR NEXT IDEA HAS A BACKEND.
Go on.
Build the real thing.
Start building for free ↗One project. The core feature set. Room to begin.