mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Wen Bo Xie
ffd2754c7a
Add two guides under Local Development for the experimental `supabase stack` commands, wire them into the docs nav, the CLI reference, the marketing features list, and the pages that readers reach with a port conflict. New pages: - guides/local-development/parallel-projects: run one local project per app, git worktree, branch, or named environment on a single machine. Covers identity, automatic port assignment, removing fixed ports from config.toml, named projects, finding endpoints, stop and destroy, the `[experimental] stack` setting, and current limitations. - guides/local-development/runtimes: the Docker and native runtimes, how the CLI picks one, native platform requirements, artifact download and cache locations, and runtime limitations. Cross-links and context: - Local development index, CLI getting started, CLI workflows, managing environments, AI tools, MCP, and the edge functions port troubleshooting entry now point readers to the new guides where a second `supabase start` fails on a port conflict. - CLI reference: `supabase stack`, `stack start`, `stack stop`, `stack destroy`, the `experimental.stack` config key, and a note on `supabase start` and `[experimental] stack`. - www: two feature entries and copy tweaks on the hosted Postgres and innovation teams solution pages. - supa-mdx-lint: allow worktree, glibc, musl, and checksum.
31 lines
2.1 KiB
Plaintext
31 lines
2.1 KiB
Plaintext
---
|
|
id: 'ai-tools'
|
|
title: 'AI Tools'
|
|
subtitle: 'Connect your AI coding agent to Supabase.'
|
|
---
|
|
|
|
Supabase provides everything you need to connect an AI coding agent to your project: a live connection to your database and platform (MCP), portable instructions your agent can reuse (Agent Skills), a one-step bundle of both (Plugin), and copy-paste prompts for tools that don't support any of the above.
|
|
|
|
<Admonition type="note">
|
|
|
|
See how these tools perform on real Supabase tasks in [Supabase Evals](/evals), our open-source benchmark for AI coding agents.
|
|
|
|
</Admonition>
|
|
|
|
## Pick your agent
|
|
|
|
<ContentListings id="ai-tools-supported-agents" />
|
|
|
|
## Key concepts
|
|
|
|
- **MCP (Model Context Protocol)**: a live connection between your agent and your actual Supabase project. Once connected, your agent can call tools to query data, run migrations, deploy Edge Functions, and more.
|
|
- **Agent Skills**: portable, on-demand instructions your agent loads when it needs Supabase- or Postgres-specific procedural knowledge. Skills don't require a live connection, and work across different agents.
|
|
- **Plugin**: a single install that bundles the MCP server and Agent Skills together for a specific agent.
|
|
- **Prompts**: static prompt files you copy into your project for agents that don't support MCP, plugins, or skills natively.
|
|
|
|
## Local projects for parallel agents
|
|
|
|
Agents that work in separate git worktrees or branches each need their own database. Otherwise migrations and seed data from one task affect another. With the experimental `supabase stack` commands turned on, `supabase start` gives each worktree or branch its own local Supabase project with its own ports and data. Agents that share one checkout and branch share a local project, so give each agent its own worktree. The commands also run without Docker on Linux and on macOS on Apple silicon, which covers agent sandboxes that have no container engine. See [Running multiple local projects](/docs/guides/local-development/running-multiple-local-projects) and [Docker and native runtimes](/docs/guides/local-development/docker-and-native-runtimes).
|
|
|
|
<ContentListings id="ai-tools-building-into-app" />
|