bowmark-mcp 1.0.1 → 2.0.0

package/README.md

@@ -1,8 +1,10 @@
 # bowmark-mcp — Bowmark MCP over stdio (Node)
 
-Bowmark gives agents pre-computed navigation recipes for public websites (skip
-explore-and-discover). The canonical server is hosted, streamable HTTP, no auth
-required: `https://api.bowmark.ai/mcp`.
+Bowmark turns the interaction-gated web into a **callable function library**.
+An agent reads the library (`get_library`), writes a short JavaScript script
+against it, and sends it to `run` — Bowmark executes it on the live sites in a
+sandbox and hands back the result. The canonical server is hosted, streamable
+HTTP, no auth required: `https://api.bowmark.ai/mcp`.
 
 This package is a **thin stdio bridge** to that hosted server, for MCP hosts
 whose client only speaks stdio, in Node-flavored environments. Tool schemas,
@@ -33,13 +35,13 @@ If your host speaks streamable HTTP, skip this bridge and connect directly to
 | Var | Meaning |
 |---|---|
 | `BOWMARK_MCP_URL` | Target MCP URL. Default `https://api.bowmark.ai/mcp?s=n` (`?s=n` attributes the install to the npm bridge). Point at `http://localhost:3001/mcp` for a local Bowmark API. |
-| `BOWMARK_API_KEY` | Optional. Forwarded as `X-Bowmark-Key`; a free key (bowmark.ai dashboard) raises the anonymous per-IP daily synthesis cap to your plan budget. |
+| `BOWMARK_API_KEY` | Optional. Forwarded as `X-Bowmark-Key`; a free key (bowmark.ai dashboard) lifts the anonymous per-IP daily cap to your plan budget. |
 
 ## Design notes (repo-internal)
 
 - **One remote session per request, retried once.** The hosted MCP is
   stateless, so a fresh connection is semantically identical and its cost (one
-  initialize round-trip) is noise next to an `ask` synthesis — and it
+  initialize round-trip) is noise next to a `run` that drives real browsers — and it
   sidesteps long-lived-connection failure modes without reconnect bookkeeping.
   Mirrors `packages/bowmark-mcp/python` (the PyPI bridge) exactly.
 - **Pass-through only.** No tool logic lives here; the agent-surfaces sync
@@ -49,9 +51,15 @@ If your host speaks streamable HTTP, skip this bridge and connect directly to
 - **`?s=n` source code** is registered in `apps/api/src/mcp-sources.ts` +
   `mcp-registry/sources.json` (npm stdio bridge channel; the PyPI bridge is
   `?s=p`).
-- **The `mcp-name: ai.bowmark/bowmark` line above is load-bearing**: the
-  official MCP Registry validates npm package ownership by finding that
-  marker in the package README. Don't remove it.
+- **npm ownership verification needs BOTH markers — the registry checks the
+  published package.json, not just the README.** The `mcp-name:
+  ai.bowmark/bowmark` line above and the `"mcpName": "ai.bowmark/bowmark"`
+  field in `package.json` are both load-bearing; don't remove either. Learned
+  the hard way 2026-07-04: `release-mcp.yml`'s registry republish failed for
+  five straight api releases (`server returned status 400: ... "NPM package
+  'bowmark-mcp' is missing required 'mcpName' field"`) because only the
+  README marker was present — the package.json field is what `mcp-publisher
+  publish` actually validates against the live npm package.
 - **Versioning is manual** (thin bridge, not the api): bump `package.json`
   when it changes. Not wired into release-please; `private` is deliberately
   absent so npm publish works — release-please doesn't manage this package.

package/dist/bridge.js

@@ -23,7 +23,7 @@
 import { Client } from "@modelcontextprotocol/sdk/client/index.js";
 import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
-import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
+import { CallToolRequestSchema, ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";
 export const DEFAULT_URL = "https://api.bowmark.ai/mcp?s=n";
 export function targetUrl(env = process.env) {
     return env.BOWMARK_MCP_URL?.trim() || DEFAULT_URL;
@@ -35,7 +35,7 @@ export function authHeaders(env = process.env) {
     return key ? { "X-Bowmark-Key": key } : undefined;
 }
 async function withRemote(fn) {
-    const client = new Client({ name: "bowmark-mcp-bridge", version: "1.0.1" });
+    const client = new Client({ name: "bowmark-mcp-bridge", version: "2.0.0" });
     const headers = authHeaders();
     const transport = new StreamableHTTPClientTransport(new URL(targetUrl()), {
         requestInit: headers ? { headers } : undefined,
@@ -60,7 +60,7 @@ export async function callRemote(fn, connect = withRemote) {
     }
 }
 export function buildServer(remote = callRemote) {
-    const server = new Server({ name: "bowmark", version: "1.0.1" }, { capabilities: { tools: {} } });
+    const server = new Server({ name: "bowmark", version: "2.0.0" }, { capabilities: { tools: {} } });
     server.setRequestHandler(ListToolsRequestSchema, async () => {
         return await remote((c) => c.listTools());
     });

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "bowmark-mcp",
-  "version": "1.0.1",
-  "description": "Bowmark MCP over stdio \u2014 a thin bridge to the hosted Bowmark MCP at https://api.bowmark.ai/mcp",
+  "version": "2.0.0",
+  "mcpName": "ai.bowmark/bowmark",
+  "description": "Bowmark MCP over stdio \u2014 a thin bridge to the hosted Bowmark MCP at https://api.bowmark.ai/mcp. The web as callable functions: read a typed library, write a script, Bowmark runs it on the live sites.",
   "license": "MIT",
   "author": "Bowmark AI <christopher@bowmark.ai>",
   "homepage": "https://bowmark.ai",