bowmark-mcp 1.0.0 → 1.0.1
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 +18 -8
- package/dist/bridge.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -64,15 +64,25 @@ injected at the `callRemote`/`buildServer` seams.
|
|
|
64
64
|
|
|
65
65
|
## Publishing to npm
|
|
66
66
|
|
|
67
|
-
**Live since 2026-07-04** (
|
|
67
|
+
**Live since 2026-07-04** (published by CI + cold-verified via
|
|
68
68
|
`npx -y bowmark-mcp` against prod). To ship a version: **bump `version` in
|
|
69
|
-
`package.json` (and the two `version` literals in `src/bridge.ts`)
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
69
|
+
`package.json` (and the two `version` literals in `src/bridge.ts`) and
|
|
70
|
+
merge.** The actual publish does NOT run in this monorepo's CI — this repo
|
|
71
|
+
is private, and npm Trusted Publishing (OIDC) validates against
|
|
72
|
+
`package.json`'s `repository.url`, which (correctly) points at the public
|
|
73
|
+
mirror `github.com/bowmark-ai/mcp`, not `Metroxe/bowmark`. So merging here
|
|
74
|
+
only lands the version bump; `release-bowmark-mcp.yml` mirror-syncs it to
|
|
75
|
+
`bowmark-ai/mcp`, and THAT repo's own `.github/workflows/publish.yml`
|
|
76
|
+
(source-controlled at
|
|
77
|
+
[`packages/bowmark-mcp/.github/workflows/publish.yml`](../.github/workflows/publish.yml)
|
|
78
|
+
in this monorepo, mirrored in like any other file) does the real `npm
|
|
79
|
+
publish`. Auth is npm **Trusted Publishing** (OIDC) — no token, configured
|
|
80
|
+
on npmjs.com (package Settings → Trusted Publisher → GitHub Actions, repo
|
|
81
|
+
`bowmark-ai/mcp`, workflow `publish.yml`). Publishing from the public
|
|
82
|
+
mirror also auto-generates provenance attestations, which npm only produces
|
|
83
|
+
for public-repo publishes — impossible from this private monorepo
|
|
84
|
+
regardless of `repository.url`. Not release-please; the bump IS the release
|
|
85
|
+
action.
|
|
76
86
|
|
|
77
87
|
`mcp-registry/server.json` carries the matching npm `packages` entry (landed
|
|
78
88
|
after the first publish per the mcp-name ordering rule), and the website
|
package/dist/bridge.js
CHANGED
|
@@ -35,7 +35,7 @@ export function authHeaders(env = process.env) {
|
|
|
35
35
|
return key ? { "X-Bowmark-Key": key } : undefined;
|
|
36
36
|
}
|
|
37
37
|
async function withRemote(fn) {
|
|
38
|
-
const client = new Client({ name: "bowmark-mcp-bridge", version: "1.0.
|
|
38
|
+
const client = new Client({ name: "bowmark-mcp-bridge", version: "1.0.1" });
|
|
39
39
|
const headers = authHeaders();
|
|
40
40
|
const transport = new StreamableHTTPClientTransport(new URL(targetUrl()), {
|
|
41
41
|
requestInit: headers ? { headers } : undefined,
|
|
@@ -60,7 +60,7 @@ export async function callRemote(fn, connect = withRemote) {
|
|
|
60
60
|
}
|
|
61
61
|
}
|
|
62
62
|
export function buildServer(remote = callRemote) {
|
|
63
|
-
const server = new Server({ name: "bowmark", version: "1.0.
|
|
63
|
+
const server = new Server({ name: "bowmark", version: "1.0.1" }, { capabilities: { tools: {} } });
|
|
64
64
|
server.setRequestHandler(ListToolsRequestSchema, async () => {
|
|
65
65
|
return await remote((c) => c.listTools());
|
|
66
66
|
});
|
package/package.json
CHANGED