Merge pull request #98 from Ngineer101/main

feat: allow enabling of specific feature groups + adds storage tools

Author: gregnr

README.md

@@ -53,6 +53,7 @@ The following options are available:
 
 - `--read-only`: Used to restrict the server to read-only queries. Recommended by default. See [read-only mode](#read-only-mode).
 - `--project-ref`: Used to scope the server to a specific project. Recommended by default. If you omit this, the server will have access to all projects in your Supabase account. See [project scoped mode](#project-scoped-mode).
+- `--features`: Used to specify which tool groups to enable. See [feature groups](#feature-groups).
 
 If you are on Windows, you will need to [prefix the command](#windows). If your MCP client doesn't accept JSON, the direct CLI command is:
 
@@ -147,13 +148,27 @@ npx -y @supabase/mcp-server-supabase@latest --read-only
 
 We recommend you enable this by default. This prevents write operations on any of your databases by executing SQL as a read-only Postgres user. Note that this flag only applies to database tools (`execute_sql` and `apply_migration`) and not to other tools like `create_project` or `create_branch`.
 
+### Feature groups
+
+You can enable or disable specific tool groups by passing the `--features` flag to the MCP server. This allows you to customize which tools are available to the LLM. For example, to enable only the [database](#database) and [docs](#knowledge-base) tools, you would run:
+
+```shell
+npx -y @supabase/mcp-server-supabase@latest --features=database,docs
+```
+
+Available groups are: [`account`](#account), [`docs`](#knowledge-base), [`database`](#database), [`debug`](#debug), [`development`](#development), [`functions`](#edge-functions), [`storage`](#storage), and [`branching`](#branching-experimental-requires-a-paid-plan).
+
+If this flag is not passed, the default feature groups are: `account`, `database`, `debug`, `development`, `docs`, and `functions`.
+
 ## Tools
 
 _**Note:** This server is pre-1.0, so expect some breaking changes between versions. Since LLMs will automatically adapt to the tools available, this shouldn't affect most users._
 
-The following Supabase tools are available to the LLM:
+The following Supabase tools are available to the LLM, [grouped by feature](#feature-groups).
+
+#### Account
 
-#### Project Management
+Enabled by default when no `--project-ref` is passed. Use `account` to target this group of tools with the [`--features`](#feature-groups) option.
 
 _**Note:** these tools will be unavailable if the server is [scoped to a project](#project-scoped-mode)._
 
@@ -164,46 +179,66 @@ _**Note:** these tools will be unavailable if the server is [scoped to a project
 - `restore_project`: Restores a project.
 - `list_organizations`: Lists all organizations that the user is a member of.
 - `get_organization`: Gets details for an organization.
+- `get_cost`: Gets the cost of a new project or branch for an organization.
+- `confirm_cost`: Confirms the user's understanding of new project or branch costs. This is required to create a new project or branch.
 
-#### Database Operations
+#### Knowledge Base
+
+Enabled by default. Use `docs` to target this group of tools with the [`--features`](#feature-groups) option.
+
+- `search_docs`: Searches the Supabase documentation for up-to-date information. LLMs can use this to find answers to questions or learn how to use specific features.
+
+#### Database
+
+Enabled by default. Use `database` to target this group of tools with the [`--features`](#feature-groups) option.
 
 - `list_tables`: Lists all tables within the specified schemas.
 - `list_extensions`: Lists all extensions in the database.
 - `list_migrations`: Lists all migrations in the database.
 - `apply_migration`: Applies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so LLMs should use this for DDL operations (schema changes).
 - `execute_sql`: Executes raw SQL in the database. LLMs should use this for regular queries that don't change the schema.
+
+#### Debug
+
+Enabled by default. Use `debug` to target this group of tools with the [`--features`](#feature-groups) option.
+
 - `get_logs`: Gets logs for a Supabase project by service type (api, postgres, edge functions, auth, storage, realtime). LLMs can use this to help with debugging and monitoring service performance.
 - `get_advisors`: Gets a list of advisory notices for a Supabase project. LLMs can use this to check for security vulnerabilities or performance issues.
 
-#### Edge Function Management
+#### Development
+
+Enabled by default. Use `development` to target this group of tools with the [`--features`](#feature-groups) option.
+
+- `get_project_url`: Gets the API URL for a project.
+- `get_anon_key`: Gets the anonymous API key for a project.
+- `generate_typescript_types`: Generates TypeScript types based on the database schema. LLMs can save this to a file and use it in their code.
+
+#### Edge Functions
+
+Enabled by default. Use `functions` to target this group of tools with the [`--features`](#feature-groups) option.
 
 - `list_edge_functions`: Lists all Edge Functions in a Supabase project.
 - `deploy_edge_function`: Deploys a new Edge Function to a Supabase project. LLMs can use this to deploy new functions or update existing ones.
 
-#### Project Configuration
+#### Storage
 
-- `get_project_url`: Gets the API URL for a project.
-- `get_anon_key`: Gets the anonymous API key for a project.
+Disabled by default to reduce tool count. Use `storage` to target this group of tools with the [`--features`](#feature-groups) option.
+
+- `list_storage_buckets`: Lists all storage buckets in a Supabase project.
+- `get_storage_config`: Gets the storage config for a Supabase project.
+- `update_storage_config`: Updates the storage config for a Supabase project (requires a paid plan).
 
 #### Branching (Experimental, requires a paid plan)
 
+Disabled by default to reduce tool count. Use `branching` to target this group of tools with the [`--features`](#feature-groups) option.
+
 - `create_branch`: Creates a development branch with migrations from production branch.
 - `list_branches`: Lists all development branches.
 - `delete_branch`: Deletes a development branch.
 - `merge_branch`: Merges migrations and edge functions from a development branch to production.
 - `reset_branch`: Resets migrations of a development branch to a prior version.
 - `rebase_branch`: Rebases development branch on production to handle migration drift.
 
-#### Development Tools
-
-- `search_docs`: Searches the Supabase documentation for up-to-date information. LLMs can use this to find answers to questions or learn how to use specific features.
-- `generate_typescript_types`: Generates TypeScript types based on the database schema. LLMs can save this to a file and use it in their code.
-
-#### Cost Confirmation
-
-- `get_cost`: Gets the cost of a new project or branch for an organization.
-- `confirm_cost`: Confirms the user's understanding of new project or branch costs. This is required to create a new project or branch.
-
 ## Other MCP servers
 
 ### `@supabase/mcp-server-postgrest`

packages/mcp-server-supabase/src/index.test.ts

@@ -13,10 +13,11 @@ type SetupOptions = {
   accessToken?: string;
   projectId?: string;
   readOnly?: boolean;
+  features?: string[];
 };
 
 async function setup(options: SetupOptions = {}) {
-  const { accessToken = ACCESS_TOKEN, projectId, readOnly } = options;
+  const { accessToken = ACCESS_TOKEN, projectId, readOnly, features } = options;
   const clientTransport = new StreamTransport();
   const serverTransport = new StreamTransport();
 
@@ -40,6 +41,7 @@ async function setup(options: SetupOptions = {}) {
     },
     projectId,
     readOnly,
+    features,
   });
 
   await server.connect(serverTransport);

packages/mcp-server-supabase/src/platform/api-platform.ts

@@ -29,6 +29,7 @@ import {
   type ExecuteSqlOptions,
   type GetLogsOptions,
   type ResetBranchOptions,
+  type StorageConfig,
   type SupabasePlatform,
 } from './index.js';
 
@@ -600,6 +601,69 @@ export function createSupabaseApiPlatform(
 
       assertSuccess(response, 'Failed to rebase branch');
     },
+
+    // Storage methods
+    async listAllBuckets(project_id: string) {
+      const response = await managementApiClient.GET(
+        '/v1/projects/{ref}/storage/buckets',
+        {
+          params: {
+            path: {
+              ref: project_id,
+            },
+          },
+        }
+      );
+
+      assertSuccess(response, 'Failed to list storage buckets');
+
+      return response.data;
+    },
+
+    async getStorageConfig(project_id: string) {
+      const response = await managementApiClient.GET(
+        '/v1/projects/{ref}/config/storage',
+        {
+          params: {
+            path: {
+              ref: project_id,
+            },
+          },
+        }
+      );
+
+      assertSuccess(response, 'Failed to get storage config');
+
+      return response.data;
+    },
+
+    async updateStorageConfig(projectId: string, config: StorageConfig) {
+      const response = await managementApiClient.PATCH(
+        '/v1/projects/{ref}/config/storage',
+        {
+          params: {
+            path: {
+              ref: projectId,
+            },
+          },
+          body: {
+            fileSizeLimit: config.fileSizeLimit,
+            features: {
+              imageTransformation: {
+                enabled: config.features.imageTransformation.enabled,
+              },
+              s3Protocol: {
+                enabled: config.features.s3Protocol.enabled,
+              },
+            },
+          },
+        }
+      );
+
+      assertSuccess(response, 'Failed to update storage config');
+
+      return response.data;
+    },
   };
 
   return platform;

packages/mcp-server-supabase/src/platform/types.ts

@@ -1,6 +1,23 @@
+import type { InitData } from '@supabase/mcp-utils';
 import { z } from 'zod';
 import { AWS_REGION_CODES } from '../regions.js';
-import type { InitData } from '@supabase/mcp-utils';
+
+export const storageBucketSchema = z.object({
+  id: z.string(),
+  name: z.string(),
+  owner: z.string(),
+  created_at: z.string(),
+  updated_at: z.string(),
+  public: z.boolean(),
+});
+
+export const storageConfigSchema = z.object({
+  fileSizeLimit: z.number(),
+  features: z.object({
+    imageTransformation: z.object({ enabled: z.boolean() }),
+    s3Protocol: z.object({ enabled: z.boolean() }),
+  }),
+});
 
 export const organizationSchema = z.object({
   id: z.string(),
@@ -135,6 +152,9 @@ export type GenerateTypescriptTypesResult = z.infer<
   typeof generateTypescriptTypesResultSchema
 >;
 
+export type StorageConfig = z.infer<typeof storageConfigSchema>;
+export type StorageBucket = z.infer<typeof storageBucketSchema>;
+
 export type SupabasePlatform = {
   init?(info: InitData): Promise<void>;
 
@@ -146,7 +166,7 @@ export type SupabasePlatform = {
     options: ApplyMigrationOptions
   ): Promise<void>;
 
-  // Project management
+  // Account
   listOrganizations(): Promise<Pick<Organization, 'id' | 'name'>[]>;
   getOrganization(organizationId: string): Promise<Organization>;
   listProjects(): Promise<Project[]>;
@@ -188,4 +208,9 @@ export type SupabasePlatform = {
   mergeBranch(branchId: string): Promise<void>;
   resetBranch(branchId: string, options: ResetBranchOptions): Promise<void>;
   rebaseBranch(branchId: string): Promise<void>;
+
+  // Storage
+  getStorageConfig(projectId: string): Promise<StorageConfig>;
+  updateStorageConfig(projectId: string, config: StorageConfig): Promise<void>;
+  listAllBuckets(projectId: string): Promise<StorageBucket[]>;
 };