Supabase
MCP server for interacting with the Supabase platform
Descripción del creador (original en inglés)
Postgres backend your coding agent builds over MCP; destructive actions wait for a person.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
BACKENLY_API_KEY, BACKENLY_PROJECT, BACKENLY_API_URLLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://backenly.com/api/mcpAbre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"backenly": {
"command": "npx",
"args": [
"-y",
"@backenly/mcp-server"
],
"env": {
"BACKENLY_API_KEY": "your-value",
"BACKENLY_PROJECT": "your-value",
"BACKENLY_API_URL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add --transport http backenly https://backenly.com/api/mcpclaude mcp add backenly --env BACKENLY_API_KEY=your-value --env BACKENLY_PROJECT=your-value --env BACKENLY_API_URL=your-value -- npx -y @backenly/mcp-serverCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"backenly": {
"url": "https://backenly.com/api/mcp"
}
}
}Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"backenly": {
"command": "npx",
"args": [
"-y",
"@backenly/mcp-server"
],
"env": {
"BACKENLY_API_KEY": "your-value",
"BACKENLY_PROJECT": "your-value",
"BACKENLY_API_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"backenly": {
"type": "http",
"url": "https://backenly.com/api/mcp"
}
}
}Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"backenly": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@backenly/mcp-server"
],
"env": {
"BACKENLY_API_KEY": "your-value",
"BACKENLY_PROJECT": "your-value",
"BACKENLY_API_URL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://backenly.com/api/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
BACKENLY_PROJECT envBACKENLY_API_URL envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub backenly, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; revisamos los endpoints por turnos
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: BACKENLY_API_KEY
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez –, y la última versión (0.4.0) llegó al registro hace 13 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP server for interacting with the Supabase platform
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Plug [Backenly](https://backenly.com) into Claude Code, Cursor, Codex, Cline, and Claude Desktop over the Model Context Protocol.
claude mcp add backenly -- npx -y @backenly/mcp-server \
--project --key mcp_live_...
Run it before you open the agent: hosts read MCP config when a conversation starts, so the tools appear in the next conversation, not the one that ran the command. An agent that installs it mid-conversation keeps working through npx -y @backenly/cli@latest call , which reaches the same tools with the same key.
Twenty-three advertised tools, not sixty. The catalog is an allowlist admitted on one rule — *is there exactly one tool here that answers a given request?* — because tool-selection accuracy degrades with catalog size and models misfire hardest between similarly-named tools. Everything else is reached through backend_chat. Unlisted tools stay dispatchable, so clients pinned to an older manifest keep working.
backend_chat — say what you want> Add comments and likes to my posts table
The host LLM hands the request to Backenly's brain. Brain plans, executes, and returns a summary. The host LLM never has to learn a vocabulary.
read_backend_state — the single read-state door. Call with no arguments for the grounding overview; pass section (schema, tables, apis, rls, metrics, errors, deploy, usage, autonomy, …) to drill in. It replaces the ~26 list_* / get_* tools, which remain dispatchable.run_query — standard read-only SQL over your workspace schema: joins, GROUP BY, aggregates, window functions, CTEs, EXPLAIN. Runs as a SELECT-only Postgres role scoped to the project, so isolation is a database grant rather than a parser. Secret-bearing columns come back redacted.get_table_schema — everything about one table: columns, foreign keys, indexes, CHECK constraints with their permitted values, and live RLS policies. Read it before any write.generate_types — TypeScript types (or a typed client, or OpenAPI) from the live catalog, with a schemaHash for drift checks.fetch_docs — pull current Backenly docs instead of guessing.check_approval — poll an escalated destructive request.apply_migration — ordinary PostgreSQL DDL (CREATE TABLE, ALTER TABLE, CREATE INDEX), translated statement by statement into governed actions. All-or-nothing; anything it cannot govern is refused with the tool to use instead. Not raw SQL execution.db_insert / db_update / db_delete — row writes. Owner-level: validates shapes but bypasses end-user RLS and triggers, so treat them as maintenance tools.set_rls — a row-level security predicate installed verbatim and read back from pg_policies.One tool per dashboard section, each with an action: auth, storage, functions, realtime, integrations, monitoring, autonomy, webhooks, deploy, connect, plus branch (preview branches). Each tool's description lists its actions and their arguments. Destructive and high-risk actions (deploy, rollback, deletes, revoking a key) park the exact call for a human and run it verbatim once approved; poll check_approval. REST endpoints need no generation step, and older tool names such as enable_auth or adopt_external_schema stay callable by name without being advertised.
Browse live state without spending a tool call:
backenly://state Full backend state
backenly://tables Table list + counts backenly://apis REST endpoints backenly://buckets Storage buckets backenly://triggers Event triggers backenly://rls RLS policies backenly://functions AI functions backenly://deploy Deploy status backenly://metrics Performance metrics backenly://errors Recent errors backenly://usage Plan usage
Generate a scoped key from [backenly.com](https://backenly.com) → your project → Connect → Agents. It starts with mcp_live_, only works on MCP routes, and is revocable from the same page.
Claude Code / Codex — one command:
claude mcp add backenly -- npx -y @backenly/mcp-server \
--project --key mcp_live_...
Cursor (~/.cursor/mcp.json, not the project's), Cline (cline_mcp_settings.json), Claude Desktop — same server block:
{
"mcpServers": { "backenly": { "command": "npx", "args": [ "-y", "@backenly/mcp-server", "--project", " ", "--key", "mcp_live_..." ] } } }
Prefer to keep the key out of a file you might commit? Run the installer once — it verifies the key, writes ~/.backenly/mcp.json (mode 0600), and prints config snippets. The host block then needs no key at all.
npx @backenly/mcp-server init
Open a new conversation in your host. Backenly appears as a tool surface.
The mcp_live_ key is for your agent only. Backenly's runtime API refuses it, so it never goes in app code or an app's environment: the app gets its own key from connect { action: "create_api_key" }, or Settings → API keys.
Host LLM (Claude Code, Cursor, ...)
│ stdio JSON-RPC ▼ @backenly/mcp-server (this package) │ HTTPS + x-api-key + x-correlation-id ▼ backenly.com — brain, executor, runtime APIs
The package contains zero business logic — it's a thin protocol adapter. Tool definitions, billing, rate limiting, and audit logging all live server-side. New brain tools appear in your host immediately without npm update.
Built on the official MCP TypeScript SDK (v2). It serves both protocol eras from one server: hosts that open with initialize (revisions 2024-11-05 through 2025-11-25) and hosts that speak 2026-07-28 (server/discover, per-request _meta). Requires Node.js 20 or newer.
Every tool result carries the server's JSON body twice: as structuredContent, for hosts that read fields (ok, code, hint, applied, approval, …), and as text, for hosts that only read text. A failure adds a second text block saying what its fields mean for the next step. Fields the server did not send stay absent.
What this package serves (tools, instructions, resources, result shapes) is what the remote endpoint (https://backenly.com/api/mcp) serves, and CI compares the two call for call.
502/503/504 retry with exponential backoff (250ms / 1s / 3s + jitter), honoring Retry-After./api/mcp/health runs before manifest fetch so auth failures surface in <1s.x-correlation-id for distributed tracing.mcp_live_…) are scope-gated — /api/mcp/* rejects runtime SDK keys. A leaked SDK key cannot be replayed against MCP to drop tables.drop_table, delete_bucket, truncate_table, etc. are never executed from MCP. Ask for one via backend_chat and it parks in the project's Review Queue and returns an approval id; a human decides in the dashboard and you poll check_approval until it is executed or rejected. The agent cannot self-approve.ApiKey.rateLimit / rateLimitWindow. 429 includes Retry-After + X-RateLimit-* headers.AuditLog row on your project timeline.0600 permissions (user-only readable).| Variable | Default | Notes |
|---|---|---|
BACKENLY_API_KEY | from ~/.backenly/mcp.json | Override key (CI / multiple projects). |
BACKENLY_API_URL | https://backenly.com | Self-hosted Backenly endpoint. |
npx @backenly/mcp-server init # interactive setup
npx @backenly/mcp-server init -k # setup with API key flag npx @backenly/mcp-server # run as MCP server (stdio) npx @backenly/mcp-server health # verify the configured key npx @backenly/mcp-server version npx @backenly/mcp-server help
"This key has scope='runtime'" — you pasted your SDK anon key. Generate a separate MCP key from the project's Connect → Agents page.
"Could not reach Backenly" — check your internet or set BACKENLY_API_URL if self-hosting.
Host shows "MCP server crashed" — run npx @backenly/mcp-server health to verify the key. Check ~/.backenly/mcp.json exists and has mode 0600.
Rate-limited (429) — your MCP key hit its per-minute cap. Default is 600/min; raise it from the dashboard or wait until X-RateLimit-Reset.
MIT — see LICENSE.