Conditional tools based on platform implementation

[gregnr]

Supabase MCP supports custom platform implementations based on the environment it is running in. This PR makes it more flexible by allowing you to implement only a subset of platform operations.

Before:

const myPlatform: SupabasePlatform = {
  executeSql() { ... },
  listMigrations() { ... },
  applyMigration() { ... },
  // every other possible platform operation must be implemented
}

After:

const myPlatform: SupabasePlatform = {
  // grouped by feature category now
  database: {
    executeSql() { ... },
    listMigrations() { ... },
    applyMigration() { ... },
  },
  functions: { ... },
  // option to not implement anything else
}

Why?

Self-hosted Supabase can support some but not all platform operations (e.g. it can't support account level or branching operations). In order to make this MCP server compatible with self-hosted, we need a way to conditionally provide tools based on which platform operations are available.

This also gives us the flexibility to choose a subset of features to implement on the remote MCP implementation (useful during development and quick iterations).

How?

Now that we support feature groups, we can extend this logic to also filter by platform operations. The SupabasePlatform interface is now grouped by feature (database, account, functions, etc) and each group is optional. We add logic in the server that conditionally adds tools only if the platform methods for that group are implemented.

[madhavpujara-at]

any updates on when will this be merged

[nthtrung09it]

waiting ...

[mattrossman]

LGTM ✅ Confirmed in Cursor that specifying an unimplemented --features group correctly fails the load the server, and that debug correctly falls back to debugging.