v0.4.1

What's Changed

• Fixes error "File URL path must be absolute" on the list_edge_functions tool for Windows users

By PR

• chore: add coverage reporting via coveralls by @gregnr in #73
• docs: update readme.md with troubleshooting information for npm installs by @charislam in #75
• fix: edge function path parsing on windows by @gregnr in #76

New Contributors

• @charislam made their first contribution in #75

Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's Changed

• Project scoped mode: You can now restrict the server to a specific project by setting the --project-ref flag on the CLI command:

  npx -y @supabase/mcp-server-supabase@latest --access-token=<personal-access-token> --project-ref=<project-ref>

• TimeScaleDB's internal tables from the _timescaledb_internal schema are now excluded from list_tables. This fixes issues where folks would use up their entire context window by a massive result from list_tables (many MB).

Breaking changes

• The list_tables tool call now requires the LLM to pass a schema array (previously optional). This was primarily to fix a Cursor bug when no args were passed to list_tables, but also provides a better default for querying only tables in the public/auth schemas.

By PR

• fix: exclude timescale internal schema from list_tables by @gregnr in #65
• feat: project scoped server option by @gregnr in #63

Full Changelog: v0.3.6...v0.4.0

v0.3.6

What's Changed

• Edge Functions! You can now retrieve and deploy Edge Functions via MCP.

By PR

• chore: link branching docs in readme by @sweatybridge in #56
• feat: list and deploy edge functions by @gregnr in #58

Full Changelog: v0.3.5...v0.3.6

v0.3.5

What's Changed

• You can now use the --read-only flag to force all SQL queries to run as a read-only Postgres user. This is useful if you want to connect your AI agent with Supabase for query purposes but don't want to risk AI modifying your database.

• Fixes the following Windsurf error when calling tools that take no parameters:

  [ { "code": "invalid_type", "expected": "object", "received": "undefined", "path": [], "message": "Required" } ] (Code -32603)
  

By PR

• chore: document branching for MCP and production workflow by @sweatybridge in #46
• feat: llm e2e tests by @gregnr in #48
• Global read only mode by @gregnr in #47
• fix: tool calls with undefined args by @gregnr in #50

Full Changelog: v0.3.4...v0.3.5

v0.3.4

What's Changed

• Fixed a bug where get_tables pulls in tables from system schemas which blows up the LLM's context window.

By PR

• fix: remove system schemas from table list by @gregnr in #44

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

Windows users: this version fixes a bug where the npx command failed to run and could not be used with any client. This was caused by a nested C++ dependency trying to build itself during install and failing. Fixed by removing the dependency, more info in #43.

By PR

• fix: remove pg-meta dep by embedding required logic by @gregnr in #43

Full Changelog: v0.3.2...v0.3.3

v0.3.2

What's Changed

• Add support for SUPABASE_ACCESS_TOKEN environment variable by @toyamarinyon in #39

New Contributors

• @toyamarinyon made their first contribution in #39

Full Changelog: v0.3.0...v0.3.2

v0.3.0

Breaking changes

• create_project and create_branch tools now require confirm_cost_id arg. Since both of these resources cost money, we need explicit confirmation from the user before creating them. The new flow is:
  • LLM calls get_cost to get the cost of a new project/branch for your organization and shares it with the user
  • LLM call confirm_cost which the user must accept to indicate that they confirm their understanding of the resource's cost
  • LLM sends the resulting confirmation ID from confirm_cost to either create_project or create_branch
  • Without this confirmation ID, create_project and create_branch will throw an error

By PR

• feat: cost confirmation flows by @gregnr in #21
• refactor: more explicit tests by @gregnr in #37
• feat: cli flag to show version by @gregnr in #36
• fix: error when fetching edge function logs by @gregnr in #34
• fix: tool param not set to default value when omitted by @gregnr in #35

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Breaking changes

• enable_branching tool removed - this is now implicit when creating your first branch

Other changes

• get_logs now supports branch-action service type that allows the LLM to debug branching operations

By PR

• docs: clarify cli usage by @gregnr in #17
• feat: add branch action logs by @sweatybridge in #18
• chore: remove enable branching tool by @sweatybridge in #19

Full Changelog: v0.1.2...v0.2.0

v0.1.2

What's Changed

• get_logs tool call by @gregnr in #13
• feat: support resetting branch to a specific migration version by @sweatybridge in #14

Full Changelog: v0.1.1...v0.1.2