Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ Enabled by default. Use `debugging` to target this group of tools with the [`fea
Enabled by default. Use `development` to target this group of tools with the [`features`](#feature-groups) option.

- `get_project_url`: Gets the API URL for a project.
- `get_anon_or_publishable_keys`: Gets the anonymous API keys for a project. Returns an array of client-safe API keys including legacy anon keys and modern publishable keys. Publishable keys are recommended for new applications.
- `get_publishable_keys`: Gets the anonymous API keys for a project. Returns an array of client-safe API keys including legacy anon keys and modern publishable keys. Publishable keys are recommended for new applications.
- `generate_typescript_types`: Generates TypeScript types based on the database schema. LLMs can save this to a file and use it in their code.

#### Edge Functions
Expand Down
2 changes: 1 addition & 1 deletion docs/production.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ When creating a migration that inserts static data, it is important to ask the L

When creating a destructive migration like dropping a column, you must review the generated SQL statements and the current state of your database to confirm that the data loss is expected and acceptable.

After successfully applying a migration, you can test your database changes by connecting your app to the development branch. The branch project URL and API keys can be fetched using `get_project_url` and `get_anon_key` tools respectively. Save them in your `.env` file to avoid repeating this in the future.
After successfully applying a migration, you can test your database changes by connecting your app to the development branch. The branch project URL and API keys can be fetched using `get_project_url` and `get_publishable_keys` tools respectively. Save them in your `.env` file to avoid repeating this in the future.

### Revert a migration

Expand Down
2 changes: 1 addition & 1 deletion packages/mcp-server-supabase/package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@supabase/mcp-server-supabase",
"mcpName": "com.supabase/mcp",
"version": "0.5.8",
"version": "0.5.9",
"description": "MCP server for interacting with Supabase",
"license": "Apache-2.0",
"type": "module",
Expand Down
4 changes: 2 additions & 2 deletions packages/mcp-server-supabase/server.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
"subfolder": "packages/mcp-server-supabase"
},
"websiteUrl": "https://supabase.com/mcp",
"version": "0.5.8",
"version": "0.5.9",
"remotes": [
{
"type": "streamable-http",
Expand All @@ -20,7 +20,7 @@
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org",
"identifier": "@supabase/mcp-server-supabase",
"version": "0.5.8",
"version": "0.5.9",
"transport": {
"type": "stdio"
},
Expand Down
2 changes: 1 addition & 1 deletion packages/mcp-utils/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@supabase/mcp-utils",
"version": "0.2.3",
"version": "0.2.4",
"description": "MCP utilities",
"license": "Apache-2.0",
"type": "module",
Expand Down