← all repositories
butterbase-ai/butterbase

Supabase-shaped, but built for agents to drive

An open-source BaaS that exposes its entire surface—Postgres, auth, functions, storage—as MCP tools so LLMs can operate the backend directly.

1.5k stars TypeScript Coding AssistantsLLMOps · Eval
butterbase
Velocity · 7d
+76
★ / day
Trend
steady
star history

What it does Butterbase is a self-hostable backend-as-a-service: Postgres with row-level security, serverless functions on Deno, file storage, KV, realtime WebSockets, auth, and an AI gateway. The managed version lives at butterbase.ai; this repo is the runtime data plane you can run yourself.

The interesting bit Every capability is surfaced as an MCP tool at /mcp or via npx @butterbase/mcp. The project also ships a Claude Code plugin with 30+ guided skills—idea to deploy—so an agent can scaffold and operate the backend without writing glue scripts. It’s a bet that the next interface to infrastructure isn’t a dashboard, but a chat thread.

Key highlights

  • Three isolated Postgres planes: control, runtime, and per-app data with RLS
  • Durable per-key actors (chat rooms, rate limiters, long-running agents) alongside serverless functions
  • Built-in RAG pipeline, LLM gateway with pluggable router adapters, and Composio integrations
  • Edge SSR and frontend hosting for Next.js / Remix / Astro, plus static/SPA deploys
  • Self-hosted AI gateway runs without upstream billing/quota enforcement; wire your own via packages/shared interfaces

Caveats

  • Local setup is involved: Docker, Node 22+, manual migrations, seeding a dev user, and submodules (the Claude Code plugin is a separate repo)
  • Schema is not applied automatically on container start; you must run npm run migrate:all after docker compose up
  • The demo GIF placeholder in the README is commented out, so no visual quick reference exists yet

Verdict Worth a look if you’re building AI-native apps and want the backend to be agent-operable from day one. Skip it if you need a one-click managed experience; the self-host path is explicitly “bring your own orchestration.”

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.