Managing Supabase

Managing Supabase

Tools for comprehensive Supabase project management via the official MCP server.

Important: All tools require a parameter object. Pass {} for tools with no required parameters.

Tools

Account & Projects

Database

Development

Edge Functions

Branching

Debugging

Storage

Knowledge Base

Examples

List Projects and Tables

import { list_projects, list_tables } from '@connections/supabase';

const projects = await list_projects({});

const tables = await list_tables({ project_id: 'your-project-id' });

Execute SQL Query

import { execute_sql } from '@connections/supabase';

const result = await execute_sql({
  project_id: 'your-project-id',
  query: 'SELECT * FROM users WHERE created_at > now() - interval '7 days''
});

Branch-Based Development

import { create_branch, apply_migration, merge_branch } from '@connections/supabase';

// Create feature branch
await create_branch({
  project_id: 'your-project-id',
  name: 'feature/auth'
});

// Apply migration to branch
await apply_migration({
  project_id: 'your-project-id',
  sql: 'ALTER TABLE users ADD COLUMN role TEXT;'
});

// Merge when ready
await merge_branch({
  project_id: 'your-project-id',
  branch_id: 'branch-id'
});

Deploy Edge Function

import { deploy_edge_function } from '@connections/supabase';

await deploy_edge_function({
  project_id: 'your-project-id',
  name: 'hello-world',
  code: 'Deno.serve(() => new Response("Hello!"))'
});

Security Best Practices

Common Errors

Output Format

Present results as a structured report:

Managing Supabase Report
════════════════════════
Resources discovered: [count]

Resource       Status    Key Metric    Issues
──────────────────────────────────────────────
[name]         [ok/warn] [value]       [findings]

Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]

Target ≤50 lines of output. Use tables for multi-resource comparisons.

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations