list_tables
Lists all tables within the specified schemas.
schemasproject_idrequired
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 1, 2026
Supabase projects, tables, SQL, migrations, and storage from your MCP client.
Manages Supabase projects from an MCP client: schema inspection, SQL and migrations, logs, Edge Functions, storage buckets and preview branches.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
appbase puts a Supabase account within reach of an MCP client or a terminal. Projects and organizations can be listed, inspected, created, paused, and restored. Inside a project you can look at the schema (tables, extensions, migrations), run SQL or apply a tracked migration, read logs and security/performance advisors, fetch the project URL and publishable keys, generate TypeScript types from the live schema, list and deploy Edge Functions, manage storage buckets, and work with preview branches — create, merge, reset, rebase, and delete them.
A Supabase personal access token is required. Put it in the
SUPABASE_ACCESS_TOKEN environment variable; it is sent to the
Supabase Management API as a Bearer token and never appears in
output. When the variable is missing, every call fails with an error
that names it.
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Every MCP tool is also a CLI subcommand. Tool arguments are passed as
one JSON object with --json; project-scoped tools take the project
reference as project_id:
Results print as JSON. Exit codes: 0 on success, 1 when an API
call fails (including a missing SUPABASE_ACCESS_TOKEN), 2 for
usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
MCP client configuration:
All calls go to https://api.supabase.com/v1. SQL tools POST to the
project's database/query endpoint; list_tables and
list_extensions are catalog queries through that same endpoint, and
all other SQL passes through exactly as given.
MIT — see LICENSE.
Source: README.md at commit 8cc7b4a
Lists all tables within the specified schemas.
schemasproject_idrequiredLists all extensions in the database.
project_idrequiredLists all migrations in the database.
project_idrequiredExecutes raw SQL in the database.
queryrequiredproject_idrequiredApplies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so use this for DDL operations (schema changes).
namerequiredqueryrequiredproject_idrequiredGets logs for a Supabase project by service (api, postgres, edge-function, auth, storage, realtime, or branch-action).
servicerequiredproject_idrequiredGets advisory notices for a Supabase project, by type: security or performance.
typerequiredproject_idrequiredGets the API URL for a Supabase project.
project_idrequiredGets the publishable and anon API keys for a Supabase project.
project_idrequiredGenerates TypeScript types based on the database schema.
project_idrequiredincluded_schemasLists all Edge Functions in a Supabase project.
project_idrequiredGets details for an Edge Function by slug.
project_idrequiredfunction_slugrequiredDeploys an Edge Function to a Supabase project from inline files.
namerequiredfilesrequiredproject_idrequiredentrypoint_pathimport_map_pathLists all storage buckets in a Supabase project.
project_idrequiredCreates a new storage bucket in a Supabase project.
namerequiredpublicproject_idrequiredfile_size_limitallowed_mime_typesLists all development branches for a Supabase project.
project_idrequiredCreates a new development branch for a Supabase project.
namerequiredproject_idrequiredconfirm_cost_idDeletes a development branch from a Supabase project.
branch_idrequiredproject_idrequiredMerges migrations and edge functions from a development branch into production.
branch_idrequiredproject_idrequiredResets a development branch to its parent state, optionally at a migration version.
branch_idrequiredproject_idrequiredmigration_versionRebases a development branch on its parent, applying newer migrations.
branch_idrequiredproject_idrequiredLists all Supabase projects for the user.
Takes no parameters.
Gets details for a project.
idrequiredCreates a new Supabase project.
namerequiredregionconfirm_cost_idorganization_idrequiredPauses a project.
project_idrequiredRestores a project.
project_idrequiredLists all organizations that the user is a member of.
Takes no parameters.
Gets details for an organization.
idrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/appbase list_projectsdocker run -i -e SUPABASE_ACCESS_TOKEN ghcr.io/cloudcorprecords/appbaseexport SUPABASE_ACCESS_TOKEN=<your Supabase personal access token>
appbase list_projectsappbase list_tables --json '{"project_id": "abcdefghijklmnopqrst"}'appbase execute_sql --json '{"project_id": "abcdefghijklmnopqrst", "query": "select 1"}'appbase get_advisors --json '{"project_id": "abcdefghijklmnopqrst", "type": "security"}'appbase create_branch --json '{"project_id": "abcdefghijklmnopqrst", "name": "feat-x"}'
appbase --versionnpx -y @reneturcios/appbase mcp{ "mcpServers": { "appbase": { "command": "npx", "args": ["-y", "@reneturcios/appbase", "mcp"], "env": { "SUPABASE_ACCESS_TOKEN": "your Supabase personal access token" } } }}npm installnpm run build # tsc -> dist/npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev # run the CLI from source via tsx