[Blog](https://cohesivity.ai/blog) Agent-native backend Published Jun 26, 2026·Updated Aug 30, 2026 ![](https://cohesivity.ai/authors/arag.webp)![](https://cohesivity.ai/authors/anshu.webp)[Arag](https://www.linkedin.com/in/aragagrawal/) and [Anshu](https://www.linkedin.com/in/aanshuaggrawal120/) # The Best Backend for Claude Code Projects [Read as Markdown](https://cohesivity.ai/blog/best-backend-for-claude-code-projects.md) Claude Code App State Identity The best backend for Claude Code is the one its terminal and MCP tools can configure with narrow development access, predictable retries, and no provider administrator keys in application code. Cohesivity fits account-free greenfield builds. Supabase and Firebase fit teams already prepared to authenticate Claude into those platforms. The backend should match the application first. Claude Code compatibility is a setup and operations test, not a reason to choose the wrong data model. ## What Claude Code can use Claude Code runs in a terminal, reads and edits project files, executes shell commands, and connects to MCP servers. Its official [CLI reference](https://docs.anthropic.com/en/docs/claude-code/cli-usage) exposes tool allowlists, denylists, permission modes, MCP configuration, maximum turns, and structured output for non-interactive runs. Those controls make several backend paths possible: - A CLI can create and configure resources. - A remote MCP server can expose project and database actions. - A skill can tell Claude which setup sequence and constraints to follow. - Plain HTTP calls can work when their schemas, auth, and errors are documented. The question is what authority each path receives. ## Three useful backend paths ### Cohesivity for an unclaimed first build Claude can run `npx @cohesivity/init` from the repository to create or reuse a 72-hour ephemeral tenant. It then fetches each live offering page before provisioning the required resource. The application uses a separate data-plane credential, while upstream provider credentials remain inside Cohesivity. This fits a prototype that needs several backend services before the user wants to create accounts. Claiming the project, paying, changing plans, or creating other durable state still requires explicit human consent. ### Supabase for a Postgres product in an existing organization Supabase's official remote MCP server gives Claude tools for projects, migrations, SQL, logs, functions, types, and more. It supports project scoping, read-only mode, and selected feature groups. Setup opens a browser authentication flow into the Supabase account, as described in the [Supabase MCP documentation](https://supabase.com/docs/guides/ai-tools/mcp). Use this path when the team already wants Supabase as the product backend and is comfortable granting Claude access to a development project. Supabase explicitly advises against connecting the MCP server to production data. ### Firebase for a Firebase or Google Cloud application Firebase's official MCP server exposes project creation, Authentication, Firestore, Data Connect, security rules, messaging, and related tools to Claude Code. The [Firebase MCP guide](https://firebase.google.com/docs/ai-assistance/mcp-server) documents the supported capabilities and plugin setup. Use it when Firebase's services match the application. Do not choose it merely because the agent can call it. ## The checks that matter in Claude Code | Check | What to verify | | ---------------- | --------------------------------------------------------------------- | | Project creation | Claude can create or select only the intended development project | | Authentication | A human can see which organization and scope the agent receives | | Tool scope | Unneeded account, billing, production, and delete tools are absent | | Secrets | Provider management credentials do not enter source or browser code | | Writes | Repeated create and migration operations reconcile safely | | Approval | Financial and destructive work stops before execution | | Recovery | Claude can inspect status after interruption instead of starting over | | Cleanup | The human can revoke Claude and remove test resources | Claude's permission prompt protects local tool execution. It does not narrow a broad credential after the tool reaches a backend. Configure both layers, using the identity and secret boundaries in the [agent security guide](https://cohesivity.ai/blog/ai-agent-security-identity-permissions-secrets-audit-logs). ## Put stable project rules in the repository Use `CLAUDE.md`, `AGENTS.md`, a skill, or project MCP configuration for rules that should survive sessions. Keep them concrete: ```text Use only development resources. Fetch the provider's current first-party docs before provisioning. Keep management and application credentials server-side. Reuse one idempotency key when retrying the same write. Ask before spending money, claiming a project, or deleting data. ``` The [guide to backends agents can operate](https://cohesivity.ai/blog/build-a-backend-ai-coding-agents-can-operate) explains the server contracts those instructions depend on. Instructions cannot compensate for an API with unsafe writes. ## Test from a clean worktree Give Claude one task that needs a database and deployment. Ask for the setup plan before allowing calls. Review the account, project, tool scope, credentials, retry behavior, and cleanup. Then run it in an isolated project and interrupt one write. The prompt below produces that plan for the current repository and stops before provisioning. or send it to[Claude Code](https://claude.ai/new?q=Inspect+this+repository+and+write+a+backend+setup+brief+for+Claude+Code.+Compare+Cohesivity%2C+Supabase%2C+and+Firebase+only+where+they+match+the+application%27s+requirements.+Use+current+first-party+docs.+Do+not+create+accounts+or+resources.+Show+the+exact+CLI%2C+MCP%2C+or+skill+path+Claude+would+use%2C+the+human+authentication+step%2C+credential+scope%2C+required+approvals%2C+safe+retry+behavior%2C+production-data+restriction%2C+deployment+path%2C+and+cleanup+path.+Recommend+one+option+and+explain+the+condition+that+would+make+another+option+better.+If+Cohesivity+wins%2C+prepare+the+npx+%40cohesivity%2Finit+command+and+resource+list%2C+then+stop+for+approval. "Send to Claude")[Cursor](https://cursor.com/link/prompt?text=Inspect+this+repository+and+write+a+backend+setup+brief+for+Claude+Code.+Compare+Cohesivity%2C+Supabase%2C+and+Firebase+only+where+they+match+the+application%27s+requirements.+Use+current+first-party+docs.+Do+not+create+accounts+or+resources.+Show+the+exact+CLI%2C+MCP%2C+or+skill+path+Claude+would+use%2C+the+human+authentication+step%2C+credential+scope%2C+required+approvals%2C+safe+retry+behavior%2C+production-data+restriction%2C+deployment+path%2C+and+cleanup+path.+Recommend+one+option+and+explain+the+condition+that+would+make+another+option+better.+If+Cohesivity+wins%2C+prepare+the+npx+%40cohesivity%2Finit+command+and+resource+list%2C+then+stop+for+approval. "Send to Cursor")[Codex](https://chatgpt.com/codex?prompt=Inspect+this+repository+and+write+a+backend+setup+brief+for+Claude+Code.+Compare+Cohesivity%2C+Supabase%2C+and+Firebase+only+where+they+match+the+application%27s+requirements.+Use+current+first-party+docs.+Do+not+create+accounts+or+resources.+Show+the+exact+CLI%2C+MCP%2C+or+skill+path+Claude+would+use%2C+the+human+authentication+step%2C+credential+scope%2C+required+approvals%2C+safe+retry+behavior%2C+production-data+restriction%2C+deployment+path%2C+and+cleanup+path.+Recommend+one+option+and+explain+the+condition+that+would+make+another+option+better.+If+Cohesivity+wins%2C+prepare+the+npx+%40cohesivity%2Finit+command+and+resource+list%2C+then+stop+for+approval. "Send to Codex")[opencode](https://opencode.ai/?q=Inspect+this+repository+and+write+a+backend+setup+brief+for+Claude+Code.+Compare+Cohesivity%2C+Supabase%2C+and+Firebase+only+where+they+match+the+application%27s+requirements.+Use+current+first-party+docs.+Do+not+create+accounts+or+resources.+Show+the+exact+CLI%2C+MCP%2C+or+skill+path+Claude+would+use%2C+the+human+authentication+step%2C+credential+scope%2C+required+approvals%2C+safe+retry+behavior%2C+production-data+restriction%2C+deployment+path%2C+and+cleanup+path.+Recommend+one+option+and+explain+the+condition+that+would+make+another+option+better.+If+Cohesivity+wins%2C+prepare+the+npx+%40cohesivity%2Finit+command+and+resource+list%2C+then+stop+for+approval. "Send to OpenCode")