Grok Supabase apply_migration
How to: Grok Supabase apply_migration
Add Supabase to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp-server-supabase": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "<SUPABASE_ACCESS_TOKEN>"
}
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something apply_migration does. Grok lists the server's tools on connect and calls apply_migration itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Supabase's identifier in your config matches the one above exactly.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
Supabase will not start until these are set, so apply_migration never becomes available.
-
SUPABASE_ACCESS_TOKEN
Same tool, other clients
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.