# Your Supabase project. Checked before it ships.

Source: https://corespeed.io/integrations/supabase

Connect Supabase to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists a project's tables and migrations, runs SQL, reads logs and the security and performance advisors, and works with branches and Edge Functions. It signs in with your own Supabase account, and applying a migration is a separate call approvals can hold.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Supabase after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Find the risk. Draft the fix

Your agent reads the advisors and the tables, then drafts the migration that closes the gap. Applying it is your call.

You ask your agent: "Check our Supabase project's security advisors. For any table with RLS off, read its columns and draft a migration that turns RLS on. Do not apply it."

It calls CoreSpeed:

- `supabase__get_advisors`: ok, 690 ms
- `supabase__list_tables`: ok, 420 ms
- `supabase__list_migrations`: ok, 310 ms

It reads from: Supabase.

### Security check: One table to lock down.

public.invoices has row level security off. A migration is drafted and not applied.

**Found**

- RLS is off on public.invoices.
- A foreign key on orders has no index.

**Drafted**

- Turn on RLS for invoices, with a read policy for each invoice's owner.

_Illustrative example · Fictional data · No migration applied_

All connectors: https://corespeed.io/docs/connectors

## From schema to migration, with you in the loop

Requests you can make once Supabase is connected. The data is fictional.

### Catch what the advisors flag

Security and performance · Advisors

- Errors: 1
- Warnings: 2
- A read-only check

### Draft the migration

Turn on RLS for invoices · Migration draft

- Table: public.invoices
- Status: Draft, not applied
- Nothing applied yet

### Apply it with a yes

The migration waits · Approvals

- Migration: invoices_enable_rls
- Project: acme-app
- Ask

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Supabase**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Which Supabase tools does my agent get?

The tools of Supabase's own hosted MCP server: database, migrations, logs, advisors, branches, Edge Functions, storage and docs. CoreSpeed holds the sign-in.

### Can the agent change my database?

Yes, if your Supabase account can. Running SQL and applying a migration are separate tool calls, and your approval policy can hold them for a person.

### Should I connect a production project?

Start with a development project or a branch. Supabase advises connecting production only when a task needs production data.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/supabase

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [Hugging Face for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/hugging-face): Search Hugging Face models, datasets, Spaces and papers from your agent, and read a repo's files, commits and discussions.
- [PostHog for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/posthog): Read PostHog insights and dashboards from your agent. Get the numbers behind a question, and mark releases on your charts.
- [Snowflake for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/snowflake): Query Snowflake from your agent under your own token and role. It finds the table, reads the columns, and runs the SQL you asked for.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Supabase MCP server: https://supabase.com/docs/guides/getting-started/mcp
- Database advisors: https://supabase.com/docs/guides/database/database-advisors

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)