Supabase Alternative MCP. Manage your entire backend infrastructure via natural conversation.

This server connects your AI client straight into your whole backend setup. You get full control over projects, databases, and secrets using natural conversation with your agent. It lets you manage infrastructure tasks without ever touching a dashboard.

When you need to see what's going on across multiple accounts, you can start by listing all the organizations linked to your account via list_organizations. After that, you retrieve every Supabase project under an organization using list_projects, which gives you the status, region, and unique ID for each one. If you only care about a specific environment, you fetch all the details on a known project by running get_project with its reference ID.

Need to get authenticated? You verify the connection metadata for the user tied to your API token using get_user.

Managing the overall lifecycle of your projects is simple. If you need a brand-new environment, you provision it entirely using create_project; that sets up Postgres, Auth, Storage, and API services right out of the gate. Conversely, if resources are eating into your budget, you hit pause by invoking pause_project, which stops the compute resources but keeps all the database data safe until you're ready to go.

When it’s time to restart, you just run restore_project and bring everything back online with zero data loss. You can view the current operational configuration settings for any project's Postgres DB using get_postgres_config, or if you need to tweak parameters like connection limits—say, adjusting max_connections—you change them directly via update_postgres_config, providing the necessary JSON payload and project reference.

For development work, isolation is everything. You can list all available development branches for a given project using list_branches, seeing their status and creation details. If you need to test a new feature without messing up production data, you create an isolated copy of that project's database using create_branch. This lets multiple people work on features simultaneously without impacting the main environment.

Security hinges on managing credentials properly. You can list all existing environment secrets for a project via list_secrets, and this tool even lets you filter by branch slug if you need to check specific dev environments. To secure new keys or tokens, you create an encrypted secret using create_secret, specifying both the name and the value; remember, these are handled with encryption at rest for maximum security.

When a credential is obsolete, you remove it completely using delete_secret. Be careful here: that action is irreversible.

Overall, this agent gives your AI client deep access to Postgres configuration management—you can view or modify settings like connection limits directly through the tool calls, triggering necessary restarts when required. You're not limited by a graphical interface; you run these commands using natural language prompts in your IDE or terminal.