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
This repo uses pnpm for package management and the active LTS version of Node.js (see versions pinned in `.nvmrc` and `"packageManager"` in `package.json`).
6
+
7
+
Clone the repo and run:
8
+
9
+
```bash
10
+
pnpm install
11
+
```
12
+
13
+
To build the MCP server and watch for file changes:
14
+
15
+
```bash
16
+
cd packages/mcp-server-supabase
17
+
pnpm dev
18
+
```
19
+
20
+
Configure your MCP client with the `file:` protocol to run the local build. You may need to restart the server in your MCP client after each change.
Optionally, configure `--api-url` to point at a different Supabase instance (defaults to `https://api.supabase.com`)
42
+
43
+
## Publishing to the MCP registry
44
+
45
+
We publish the MCP server to the official MCP registry so that it can be discovered and used by MCP clients.
46
+
Note the MCP registry does not host the server itself, only metadata about the server. This is defined in the `packages/mcp-server-supabase/server.json` file.
47
+
48
+
### Dependencies
49
+
50
+
You will need to install the MCP publisher globally if you haven't already. On macOS, you can do this with Homebrew:
51
+
52
+
```shell
53
+
brew install mcp-publisher
54
+
```
55
+
56
+
See the [MCP publisher documentation](https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/publish-server.md) for other installation methods.
57
+
58
+
### Steps
59
+
60
+
1. Update the package version in `packages/mcp-server-supabase/package.json`. Follow [semver](https://semver.org/) guidelines for versioning.
61
+
62
+
2. Update `server.json` with the new version by running:
63
+
64
+
```shell
65
+
pnpm registry:update
66
+
```
67
+
68
+
3. Download the `domain-verification-key.pem` from Bitwarden and place it in `packages/mcp-server-supabase/`. This will be used to verify ownership of the `supabase.com` domain during the login process.
69
+
70
+
> This works because of the [`.well-known/mcp-registry-auth`](https://github.com/supabase/supabase/blob/master/apps/www/public/.well-known/mcp-registry-auth) endpoint served by `supabase.com`.
Copy file name to clipboardExpand all lines: README.md
+1-37Lines changed: 1 addition & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,43 +290,7 @@ The PostgREST MCP server allows you to connect your own users to your app via RE
290
290
291
291
## For developers
292
292
293
-
This repo uses pnpm for package management and the active LTS version of Node.js (see versions pinned in `.nvmrc` and `"packageManager"` in `package.json`).
294
-
295
-
Clone the repo and run:
296
-
297
-
```bash
298
-
pnpm install
299
-
```
300
-
301
-
To build the MCP server and watch for file changes:
302
-
303
-
```bash
304
-
cd packages/mcp-server-supabase
305
-
pnpm dev
306
-
```
307
-
308
-
Configure your MCP client with the `file:` protocol to run the local build. You may need to restart the server in your MCP client after each change.
0 commit comments