MCP Database feature tools aren't listing

[ariroffe72]

Bug report

Adding the mcp with docs and database features fail to add the database tools listed in https://supabase.com/docs/guides/getting-started/mcp#database

Describe the bug

After adding the mcp server in Github Copilot CLI, and authenticating with Supabase in the browser, the tools for database are still absent

 MCP Server: supabase

 Type:     http
 URL:      https://mcp.supabase.com/mcp?project_ref={my_project}&features=docs%2Cdatabase
 Status:   ✓ Connected

 Tools (1/1 enabled):
  ✓ search_docs: Search the Supabase documentation using GraphQL. Must be a v...

To Reproduce

1. /mcp in Copilot CLI
2. Add supabase mcp url with databae features

Expected behavior

Expect database tools to be listed

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: Windows
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

Add any other context about the problem here.

[gregnr]

Hey @ariroffe72 thanks for reporting. I just tried reproducing this using the latest version of the copilot CLI (1.0.48), and it successfully listed the database + docs tools:

 MCP Server: supabase-test

 Type:     http
 URL:      https://mcp.supabase.com/mcp?project_ref=<ref>&features=docs%2Cdatabase
 Status:   ✓ Connected
 Source:   /Users/<name>/.copilot/mcp-config.json

 Tools (6/6 enabled):
  ✓ apply_migration: Applies a migration to the database. Use this when executing...
  ✓ execute_sql: Executes raw SQL in the Postgres database. Use `apply_migrat...
  ✓ list_extensions: Lists all extensions in the database.
  ✓ list_migrations: Lists all migrations in the database.
  ✓ list_tables: Lists all tables in one or more schemas. By default returns ...
  ✓ search_docs: Search the Supabase documentation using GraphQL. Must be a v...

 e: edit · r: re-auth · Esc: back

Could you confirm which CLI version you are using and try again using the latest if you're not already on it?

[ariroffe72]

I updated the CLI to 1.0.48 from 1.0.44 and still experiencing this issue. On the Auth page in the browser, I do see many admin permissions that I am approving for my org as well.