Supabase

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.mcp-dir/supabase-mcp and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 20 Sept 2026. Not supplied by the maker.

• supabase_search_docs

  Search the Supabase documentation using GraphQL. Must be a valid GraphQL query. You should default to calling this even if you think you already know the answer, since the documentation is always bein

• supabase_list_organizations

  Lists all organizations that the user is a member of.

• supabase_get_organization

  Gets details for an organization. Includes subscription plan. Bulk support: accepts ids for batched execution.

• supabase_list_projects

  Lists all Supabase projects for the user. Use this to help discover the project ID of the project that the user is working on.

• supabase_get_project

  Gets details for a Supabase project. Bulk support: accepts ids for batched execution.

• supabase_get_cost

  Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.

• supabase_confirm_cost

  Ask the user to confirm their understanding of the cost of creating a new project or branch. Call `get_cost` first. Returns a unique ID for this confirmation which should be passed to `create_project`

• supabase_create_project

  Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use `get_project` to check the status. Bulk support

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.