@rebasepro/mcp 0.19.2-canary.gef769df → 0.20.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +31 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -214,6 +214,37 @@ Add to your AI assistant's MCP config (e.g. `.gemini/settings.json`):
|
|
|
214
214
|
}
|
|
215
215
|
```
|
|
216
216
|
|
|
217
|
+
## MCP Registry
|
|
218
|
+
|
|
219
|
+
A stable release publishes this server to the
|
|
220
|
+
[MCP Registry](https://registry.modelcontextprotocol.io) as
|
|
221
|
+
`io.github.rebasepro/rebase` — the listing MCP clients read when they offer an
|
|
222
|
+
install. Two files carry that identity, and they must agree:
|
|
223
|
+
|
|
224
|
+
| | |
|
|
225
|
+
|---|---|
|
|
226
|
+
| `package.json` → `mcpName` | the ownership proof, read out of the **published npm tarball** |
|
|
227
|
+
| `server.json` | the manifest: the same name, the version, and the npm package to install |
|
|
228
|
+
|
|
229
|
+
Neither is edited by hand on a release. `publishable-packages.mjs --set-version`
|
|
230
|
+
writes the version into `server.json` alongside every `package.json`, and
|
|
231
|
+
`pnpm check:publishable-set` refuses a tree where the two disagree — the registry
|
|
232
|
+
validates a publish by downloading the tarball the manifest names, so a manifest
|
|
233
|
+
left behind fails the release at its last step, once npm can no longer be
|
|
234
|
+
rewritten.
|
|
235
|
+
|
|
236
|
+
The stable publish workflow pushes the registry entry itself, after npm, the tag
|
|
237
|
+
and the fleet image, on the OIDC token it already holds for npm provenance. A
|
|
238
|
+
hand-run `release.sh` cannot — the login is a device-code flow — so it prints
|
|
239
|
+
the command to finish the job:
|
|
240
|
+
|
|
241
|
+
```bash
|
|
242
|
+
mcp-publisher login github && mcp-publisher publish
|
|
243
|
+
```
|
|
244
|
+
|
|
245
|
+
Install `mcp-publisher` with `brew install mcp-publisher`, and check a manifest
|
|
246
|
+
without publishing anything using `mcp-publisher validate`.
|
|
247
|
+
|
|
217
248
|
## Related Packages
|
|
218
249
|
|
|
219
250
|
- `@rebasepro/client` — Used internally for data and admin API calls
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@rebasepro/mcp",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.20.0",
|
|
4
4
|
"description": "Model Context Protocol Server for Rebase — exposes schema, DB, document, and user management tools to AI assistants.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"rebase",
|
|
@@ -40,7 +40,7 @@
|
|
|
40
40
|
"dependencies": {
|
|
41
41
|
"@modelcontextprotocol/sdk": "^1.30.0",
|
|
42
42
|
"dotenv": "^17.4.2",
|
|
43
|
-
"@rebasepro/client": "0.
|
|
43
|
+
"@rebasepro/client": "0.20.0"
|
|
44
44
|
},
|
|
45
45
|
"devDependencies": {
|
|
46
46
|
"@types/node": "^26.1.2",
|