bowmark-mcp 0.1.0 → 1.0.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 CHANGED
@@ -64,16 +64,16 @@ injected at the `callRemote`/`buildServer` seams.
64
64
 
65
65
  ## Publishing to npm
66
66
 
67
- To ship a version: **bump `version` in `package.json` (and the two
68
- `version: "0.1.0"` literals in `src/bridge.ts`) and merge** —
69
- `.github/workflows/publish-bowmark-mcp.yml` compares the manifest against
70
- live npm on every merge touching this folder and publishes only when the
71
- version is new (requires the `NPM_TOKEN_BOWMARK_MCP` Actions secret; token
72
- lives in the 1Password item "npm bowmark-mcp publish token"). Not
73
- release-please; the bump IS the release action.
74
-
75
- After the FIRST publish: add an npm `packages` entry to
76
- `mcp-registry/server.json` (same after-publish ordering rule as PyPI — the
77
- registry validates the `mcp-name` marker on the live npm README), and swap
78
- the website stdio tab's Node step from `npx mcp-remote` to
79
- `npx bowmark-mcp`.
67
+ **Live since 2026-07-04** (v0.1.0, published by CI + cold-verified via
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
+ and merge** — `.github/workflows/publish-bowmark-mcp.yml` compares the
71
+ manifest against live npm on every merge touching this folder and publishes
72
+ only when the version is new (requires the `NPM_TOKEN_BOWMARK_MCP` Actions
73
+ secret; token lives in the 1Password item "npm bowmark-mcp publish token" —
74
+ 90-day expiry, so consider switching the workflow to npm Trusted Publishing).
75
+ Not release-please; the bump IS the release action.
76
+
77
+ `mcp-registry/server.json` carries the matching npm `packages` entry (landed
78
+ after the first publish per the mcp-name ordering rule), and the website
79
+ stdio tab's Node step points at `npx bowmark-mcp`.
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: "0.1.0" });
38
+ const client = new Client({ name: "bowmark-mcp-bridge", version: "1.0.0" });
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: "0.1.0" }, { capabilities: { tools: {} } });
63
+ const server = new Server({ name: "bowmark", version: "1.0.0" }, { capabilities: { tools: {} } });
64
64
  server.setRequestHandler(ListToolsRequestSchema, async () => {
65
65
  return await remote((c) => c.listTools());
66
66
  });
package/package.json CHANGED
@@ -1,13 +1,13 @@
1
1
  {
2
2
  "name": "bowmark-mcp",
3
- "version": "0.1.0",
3
+ "version": "1.0.0",
4
4
  "description": "Bowmark MCP over stdio \u2014 a thin bridge to the hosted Bowmark MCP at https://api.bowmark.ai/mcp",
5
5
  "license": "MIT",
6
6
  "author": "Bowmark AI <christopher@bowmark.ai>",
7
7
  "homepage": "https://bowmark.ai",
8
8
  "repository": {
9
9
  "type": "git",
10
- "url": "git+https://github.com/bowmark-ai/bowmark-mcp.git",
10
+ "url": "git+https://github.com/bowmark-ai/mcp.git",
11
11
  "directory": "node"
12
12
  },
13
13
  "keywords": [