supabase / mcp / 29371236576

96%

push

github

docs: breaking change strategy (#330)

Documents a breaking change strategy for the MCP server in
`CONTRIBUTING.md`, as we prepare for various tool changes and strict
output schemas.

The main risk is our ChatGPT Plugin (previously App) submission which
freezes server metadata including the tools list, see their [Ongoing
Maintenance](https://developers.openai.com/apps-sdk/deploy/submission#ongoing-maintenance)
docs. I'm advising a parallel change / expand-and-contract workflow to
keep changes backwards compatible.

Claude Connectors don't appear to have this risk. From [Manage your
listing after
publishing](https://claude.com/docs/connectors/building/after-publishing#update-your-mcp-server):

> An MCP server is a live API. To add, change, or remove tools, deploy
the change to your server—no resubmission to Anthropic is required, and
there is no scheduled re-review. Claude picks up the new tool surface on
the next connection.

This also removes the duplicated tools/options list from the README in
favor of linking to [supabase.com/mcp](https://supabase.com/mcp) as the
canonical source to prevent drift.

Closes AI-900

313 of 347 branches covered (90.2%)

Branch coverage included in aggregate %.

2735 of 2820 relevant lines covered (96.99%)

41.15 hits per line