feat: project scoped server option

[gregnr]

Allows you to scope the MCP server to a specific project via the --project-ref CLI flag:

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase@latest",
        "--access-token",
        "<personal-access-token>",
        "--project-ref",
        "<project-ref>"
      ]
    }
  }
}

This is useful for:

• Defining in an MCP JSON config that is committed to version control so that you can link a local project with the remote Supabase project
• Ensuring that the LLM only operates on the specified project and not others
• Reducing the number of tools

Under the hood

When you configure the server with a specific project ID, all tools that previously accepted a project_id parameter will omit that parameter from its tool definition and statically set it to the configured ID. Specifically we create an injectableTool() function that allows us to define tools with an optional inject property that performs the above logic. This allows us implement this scoping logic without duplicating every single tool definition for each mode.

Additionally we omit any account-level tools (like list_organizations, list_projects, etc) when in project scoped mode. This has the added benefit of reducing the number of tools we need for clients like Cursor who limit the total number of tools to 40.