You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -168,11 +172,11 @@ You can create project-specific MCP by:
168
172
```json
169
173
{
170
174
"mcpServers": {
171
-
"filesystem": {
172
-
"command": "supabase-mcp-server",
175
+
"supabase": {
176
+
"command": "supabase-mcp-server"
173
177
}
174
178
}
175
-
}
179
+
}
176
180
```
177
181
178
182
Alternatively, if you want to configure MCP servers globally (i.e. not for each project), you can use configure connection settings by updating an `.env` file in a global config folder by running the following commands:
SUPABASE_REGION=us-east-1 # optional, defaults to us-east-1
205
209
SUPABASE_ACCESS_TOKEN=your-access-token # optional, for management API
210
+
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key # optional, for Auth Admin SDK
206
211
```
207
212
208
213
Verify the file exists - you should see the values you have just set:
@@ -230,7 +235,8 @@ Windsurf supports de facto standard .json format for MCP Servers configuration.
230
235
"SUPABASE_PROJECT_REF": "your-project-ref",
231
236
"SUPABASE_DB_PASSWORD": "your-db-password",
232
237
"SUPABASE_REGION": "us-east-1", // optional, defaults to us-east-1
233
-
"SUPABASE_ACCESS_TOKEN": "your-access-token"// optional, for management API
238
+
"SUPABASE_ACCESS_TOKEN": "your-access-token", // optional, for management API
239
+
"SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key"// optional, for Auth Admin SDK
234
240
}
235
241
}
236
242
}
@@ -279,7 +285,8 @@ Go to Cascade -> Click on the hammer icon -> Configure -> Fill in the configurat
279
285
"SUPABASE_PROJECT_REF": "your-project-ref",
280
286
"SUPABASE_DB_PASSWORD": "your-db-password",
281
287
"SUPABASE_REGION": "us-east-1", // optional, defaults to us-east-1
282
-
"SUPABASE_ACCESS_TOKEN": "your-access-token"// optional, for management API
288
+
"SUPABASE_ACCESS_TOKEN": "your-access-token", // optional, for management API
289
+
"SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key"// optional, for Auth Admin SDK
283
290
}
284
291
}
285
292
}
@@ -386,6 +393,7 @@ Since v0.3.0 server supports sending arbitrary requests to Supabase Management A
386
393
- Divides API methods into `safe`, `unsafe` and `blocked` categories based on the risk of the operation
387
394
- Allows to switch between safe and unsafe modes dynamically
388
395
- Blocked operations (delete project, delete database) are not allowed regardless of the mode
396
+
- **Note**: Management API tools only work with remote Supabase instances and are not compatible with local Supabase development setups.
389
397
390
398
### Auth Admin tools
391
399
I was planning to add support for Python SDK methods to the MCP server. Upon consideration I decided to only add support for Auth admin methods as I often found myself manually creating test users which was prone to errors and time consuming. Now I can just ask Cursor to create a test user and it will be done seamlessly. Check out the full Auth Admin SDK method docs to know what it can do.
0 commit comments