Supabase Coolify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | The URL of your Supabase instance (e.g., https://your-supabase-instance.example.com) | |
| COOLIFY_API_URL | Yes | The URL of your Coolify instance (e.g., http://localhost:8000) | |
| COOLIFY_TEAM_ID | No | Optional Coolify team ID | |
| SUPABASE_DB_HOST | No | Direct database host (e.g., localhost) | |
| SUPABASE_DB_NAME | No | Direct database name (e.g., postgres) | |
| SUPABASE_DB_PORT | No | Direct database port (e.g., 5432) | |
| SUPABASE_DB_USER | No | Direct database user (e.g., postgres) | |
| COOLIFY_API_TOKEN | Yes | Your Coolify API token with appropriate permissions | |
| SUPABASE_ANON_KEY | No | Your Supabase anonymous key | |
| SUPABASE_PROJECT_ID | No | Your Supabase project ID | |
| SUPABASE_DB_PASSWORD | No | Direct database password | |
| SUPABASE_PROJECT_REF | No | Your Supabase project reference | |
| SUPABASE_FUNCTIONS_URL | No | The URL for Supabase Edge Functions (e.g., https://your-supabase-instance.example.com/functions/v1) | |
| SUPABASE_SERVICE_ROLE_KEY | Yes | Your Supabase service role key (keep this secure!) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_migrationsB | List all database migrations with their status |
| deploy_migrationA | Deploy a new database migration. NOTE: For self-hosted Supabase, consider using supabase_migration_new + supabase_db_push instead for better reliability. |
| execute_sqlA | Execute raw SQL query on Supabase database. NOTE: For self-hosted Supabase, use supabase_cli_execute with "db execute" for better reliability. |
| get_migration_statusB | Get status of a specific migration |
| list_edge_functionsA | List all deployed edge functions |
| deploy_edge_functionC | Deploy a new edge function |
| delete_edge_functionC | Delete an edge function |
| get_edge_function_logsB | Get logs for an edge function |
| invoke_edge_functionC | Invoke an edge function |
| list_storage_bucketsA | List all storage buckets |
| create_storage_bucketC | Create a new storage bucket |
| delete_storage_bucketB | Delete a storage bucket |
| get_auth_configA | Get authentication configuration |
| update_auth_configC | Update authentication configuration |
| check_supabase_healthC | Check health of all Supabase services |
| get_supabase_versionB | Get Supabase version information |
| get_realtime_configD | Execute get_realtime_config |
| rollback_migrationB | Rollback a specific migration (optionally with down SQL) |
| rollback_to_versionB | Rollback all migrations after a specific version |
| rollback_last_migrationsC | Rollback the last N migrations |
| create_migration_with_rollbackB | Create a migration with both up and down SQL for safe rollbacks |
| rollback_migration_with_down_sqlB | Rollback a migration using its stored down SQL |
| check_cli_installedB | Check if Supabase CLI is installed and get version |
| supabase_initC | Initialize a new Supabase project |
| supabase_linkC | Link to a remote Supabase project |
| supabase_startB | Start local Supabase development environment |
| supabase_stopA | Stop local Supabase development environment |
| supabase_statusB | Get status of local Supabase services |
| supabase_db_diffC | Generate migration from database schema changes |
| supabase_db_pushA | Push local migrations to remote database |
| supabase_db_resetB | Reset local database to initial state |
| supabase_migration_newC | Create a new migration file |
| supabase_migration_listC | List all migrations (CLI) |
| supabase_migration_repairC | Repair migration history |
| supabase_functions_deployC | Deploy edge functions using Supabase CLI |
| supabase_functions_serveC | Serve edge functions locally |
| supabase_gen_typesC | Generate TypeScript types from database schema |
| supabase_cli_executeC | Execute arbitrary Supabase CLI command |
| list_coolify_applicationsB | List all Coolify applications |
| get_coolify_applicationC | Get details of a specific Coolify application |
| update_coolify_application_envC | Update application environment variables |
| deploy_coolify_applicationC | Deploy a Coolify application |
| start_coolify_applicationC | Start a Coolify application |
| stop_coolify_applicationB | Stop a Coolify application |
| restart_coolify_applicationB | Restart a Coolify application |
| list_coolify_servicesA | List all Coolify services |
| get_coolify_serviceA | Get details of a specific Coolify service |
| start_coolify_serviceC | Start a Coolify service |
| stop_coolify_serviceC | Stop a Coolify service |
| list_coolify_databasesC | Execute list_coolify_databases |
| get_coolify_databaseD | Execute get_coolify_database |
| get_coolify_logsB | Get application logs from Coolify |
| deploy_supabase_to_coolifyC | Deploy a complete Supabase instance on Coolify |
| update_supabase_deploymentB | Update an existing Supabase deployment |
| get_deployment_statusB | Get status of Supabase deployment on Coolify |
| verify_setupA | Verify system setup and check health of all services (Coolify, Supabase, CLI) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Database Migrations | All database migrations |
| Edge Functions | All deployed edge functions |
| Storage Buckets | All storage buckets |
| Auth Configuration | Authentication configuration |
| Service Health | Health status of all Supabase services |
| Coolify Applications | All Coolify applications |
| Coolify Services | All Coolify services |
| Coolify Databases | All Coolify databases |
TDQS
Scored across 56 tools
Tools are generally distinct by domain (Supabase vs Coolify), but overlaps exist: multiple rollback tools (rollback_last_migrations, rollback_migration, rollback_migration_with_down_sql, rollback_to_version) and edge function deployment (deploy_edge_function vs supabase_functions_deploy). Notes like execute_sql suggesting supabase_cli_execute add ambiguity.
Naming is inconsistent: some tools use verb_noun (create_migration_with_rollback), others use supabase_ prefix (supabase_db_diff), and Coolify tools mix verb_coolify_noun (deploy_coolify_application) and get/list variations (get_coolify_database vs list_coolify_databases). No consistent pattern.
56 tools is excessive for a server covering two platforms. Many tools are thin wrappers over CLI commands (supabase_*), leading to redundancy. A more focused set (20-30 tools) would be more manageable.
The tool set covers major workflows: migrations, edge functions, storage, auth, realtime for Supabase, and CRUD for Coolify applications/services. Minor gaps like database backup/restore are present, but overall lifecycle coverage is strong.