MCP server for managing self-hosted Supabase on Coolify with full deployment support
If you already use Supabase Coolify, the supabase coolify mcp server is the piece that lets your assistant work with it directly. MCP server for managing self-hosted Supabase on Coolify with full deployment support.
A comprehensive TypeScript MCP (Model Context Protocol) server for managing self-hosted Supabase on Coolify. This server enables AI agents to fully deploy migrations, push edge functions, configure services, and manage Supabase deployments with ease.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_migrations — The list_migrations tool exposed by this serverdeploy_migration — The deploy_migration tool exposed by this serverexecute_sql — The execute_sql tool exposed by this serverget_migration_status — The get_migration_status tool exposed by this serverlist_edge_functions — The list_edge_functions tool exposed by this serverdeploy_edge_function — The deploy_edge_function tool exposed by this serverdelete_edge_function — The delete_edge_function tool exposed by this serverget_edge_function_logs — The get_edge_function_logs tool exposed by this serverinvoke_edge_function — The invoke_edge_function tool exposed by this serverlist_storage_buckets — The list_storage_buckets tool exposed by this servercreate_storage_bucket — The create_storage_bucket tool exposed by this serverdelete_storage_bucket — The delete_storage_bucket tool exposed by this serverConfiguration is passed through the environment: COOLIFY_API_URL, COOLIFY_API_TOKEN, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, API_KEY, CUSTOM_VAR, COOLIFY_TEAM_ID, SUPABASE_ANON_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Supabase Coolify's toolset — list_migrations, deploy_migration, execute_sql and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dj-pearson; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_migrations | The list_migrations tool exposed by this server. |
| deploy_migration | The deploy_migration tool exposed by this server. |
| execute_sql | The execute_sql tool exposed by this server. |
| get_migration_status | The get_migration_status tool exposed by this server. |
| list_edge_functions | The list_edge_functions tool exposed by this server. |
| deploy_edge_function | The deploy_edge_function tool exposed by this server. |
| delete_edge_function | The delete_edge_function tool exposed by this server. |
| get_edge_function_logs | The get_edge_function_logs tool exposed by this server. |
| invoke_edge_function | The invoke_edge_function tool exposed by this server. |
| list_storage_buckets | The list_storage_buckets tool exposed by this server. |
| create_storage_bucket | The create_storage_bucket tool exposed by this server. |
| delete_storage_bucket | The delete_storage_bucket tool exposed by this server. |
| get_auth_config | The get_auth_config tool exposed by this server. |
| update_auth_config | The update_auth_config tool exposed by this server. |
Then configure:
```json
{
"mcpServers": {
"supabase-coolify": {
"command": "supabase-coolify-mcp",
"env": {
"COOLIFY_API_URL": "http://localhost:8000",
"COOLIFY_API_TOKEN": "your-coolify-api-token",
"SUPABASE_URL": "https://your-supabase-instance.example.com",
"SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| COOLIFY_API_URL | Endpoint or connection string the server talks to. | Yes |
| COOLIFY_API_TOKEN | Credential the server authenticates with. | Yes |
| SUPABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SUPABASE_SERVICE_ROLE_KEY | Credential the server authenticates with. | Yes |
| API_KEY | Credential the server authenticates with. | Yes |
| CUSTOM_VAR | Configuration value read at startup. | Optional |
| COOLIFY_TEAM_ID | Configuration value read at startup. | Optional |
| SUPABASE_ANON_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.