MCP · Model Context Protocol
Give your AI agent a real backend
Connect Claude Code, Cursor, Cline, Windsurf, or Claude Desktop to a live Backenly backend in one command. Describe what you need in plain English — your agent creates the database, APIs, auth, storage, and realtime for you.
- Works with
- Claude Code · Cursor · Cline · Windsurf
- Setup
- One command, 5-line config
- Tools exposed
- 50+ build, read & data tools
Quickstart
Three steps. About two minutes. Works the same in every MCP host.
Generate an MCP key
Open your project on backenly.com and go to the MCP tab. Click Generate key. Copy the key (it starts with
mcp_live_) — it’s shown only once.Run the installer
Paste your key when prompted. The installer verifies the key and writes a local config file (
~/.backenly/mcp.json, readable only by you).terminalnpx @backenly/mcp-server initAdd Backenly to your host & restart
Drop this into your host’s MCP config, then restart the host. Backenly appears as a tool surface your agent can use.
~/.claude/mcp.json{ "mcpServers": { "backenly": { "command": "npx", "args": ["-y", "@backenly/mcp-server"] } } }Prefer to keep the key in the host config instead of the local file? Use an
envblock:mcp.json (with inline key){ "mcpServers": { "backenly": { "command": "npx", "args": ["-y", "@backenly/mcp-server"], "env": { "BACKENLY_API_KEY": "mcp_live_xxxxxxxxxxxxxxxxxxxx" } } } }
Where the config lives
The five-line block above goes in the same place for every host — only the file path changes.
~/.claude/mcp.json~/.cursor/mcp.json~/.codeium/windsurf/mcp_config.jsonCline → MCP Servers → Configureclaude_desktop_config.jsonAny MCP-compatible host works — even ones not listed here. The protocol is the same everywhere.
Then just describe your backend
You don’t learn Backenly’s commands. You talk. The agent hands your request to Backenly’s brain, which plans and builds it.
›Add a comments table linked to posts, with an owner-only edit policy and a REST API.
›Give my users profiles with avatars stored in a public bucket.
›Add full-text search over my articles table.
›Create a daily cron job that emails users their unread notifications.
What your agent can do
50+ tools across four tiers, fetched live from your project — new capabilities light up automatically, no package update needed.
backend_chat — the one tool that does everything
Hand a plain-English request to Backenly’s brain. It plans the change, executes it end to end, and returns a summary. Your agent never needs to memorise the full tool vocabulary.
Build tools (25+)
Precise, single-purpose operations when the agent wants explicit control.
Read tools (21)
Inspect live backend state without changing anything — cheap for the agent to call.
Runtime data CRUD
Read and write real rows in your workspace tables — perfect for seeding and debugging.
For AI agents
If you are an AI coding agent reading this page, copy the block below into your working context. It tells you exactly how to connect and use Backenly.
# Connecting to Backenly (instructions for the coding agent)
Backenly is the backend. To create or change backend resources
(database tables, REST APIs, auth, storage, realtime, triggers,
functions, cron jobs), use the Backenly MCP server — do NOT write
your own server, migrations, or SQL.
1. Ask the user to open backenly.com -> their project -> the "MCP"
tab and generate an MCP key (starts with "mcp_live_").
2. Add this to the host's MCP config, then restart the host:
{
"mcpServers": {
"backenly": {
"command": "npx",
"args": ["-y", "@backenly/mcp-server"],
"env": { "BACKENLY_API_KEY": "<the mcp_live_ key>" }
}
}
}
3. Once connected, prefer the single tool "backend_chat" for any
build request. Pass the user's request in plain English, e.g.
"add a comments table linked to posts, with an owner-only RLS
policy and a REST API". Backenly's brain plans and executes it.
4. Use read tools (list_tables, get_metrics, read_backend_state,
...) to inspect state, and db_query / db_insert / db_update /
db_delete for runtime rows.
5. Destructive operations (drop_table, delete_bucket) are NOT
available over MCP by design — they stay in the dashboard.Built to be handed to an agent
Scope-gated keys
MCP keys (mcp_live_…) only work on MCP routes. A leaked SDK key can’t be replayed to reach them.
No destructive tools
drop_table, delete_bucket and friends are never exposed over MCP — they stay behind explicit confirmation in the dashboard.
Every change audited
Each mutation writes an audit-log entry to your project timeline. Rate limits and plan quotas apply per call.
Revoke instantly
Kill any key from the MCP tab. The local config is written user-only (mode 0600).
Frequently asked
What is MCP and why do I need it?
The Model Context Protocol (MCP) is an open standard that lets AI coding agents talk to external tools. Connecting Backenly over MCP means your agent can build and run a real backend for you — instead of you copy-pasting API docs into a chat. It is the fastest way for AI-built ("vibe coded") apps to get a production backend.
Which tools and editors are supported?
Any MCP-compatible host: Claude Code, Cursor, Cline, Windsurf, and Claude Desktop today, plus any future MCP host. The setup is the same five-line config for all of them.
Do I need to know Backenly’s commands?
No. Just describe what you want in plain English. The backend_chat tool routes your request to Backenly’s brain, which plans and executes the change. The tool names are optional power-user surface, not something you have to learn.
Is it safe to give an AI agent this access?
Yes. MCP keys are scope-gated (an SDK key can’t be replayed against MCP), destructive operations like dropping tables are never exposed over MCP, every mutation is written to your audit log, and you can revoke any key instantly from the MCP tab. Plan quotas and per-key rate limits apply on every call.
What does it cost?
The MCP server package is free and open source. Usage counts against your normal Backenly plan quota and AI credits — the same as building from the dashboard.
The agent says my key has the wrong scope.
You pasted your SDK/anon key. Generate a dedicated MCP key (it starts with mcp_live_) from your project’s MCP tab and use that instead.
Point your agent at Backenly
Free to start. No credit card. Generate an MCP key and your AI editor has a production backend in minutes.