Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @bowmark/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add bowmark-mcp -- npx -y @bowmark/mcp@2.1.2Ejecútalo en una terminal.
{ "mcpServers": { "bowmark-mcp": { "command": "npx", "args": [ "-y", "@bowmark/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirLM Studio — GitHub strips a raw lmstudio: link, so this one is a paste, not a button. Copy it into your browser's address bar:
lmstudio://add_mcp?name=bowmark&config=eyJ1cmwiOiJodHRwczovL2FwaS5ib3dtYXJrLmFpL21jcC9iYWRnZS1sbXN0dWRpbyJ9
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.
Some MCP hosts only speak stdio — browser-use, and many self-built agent stacks. This repo holds two thin stdio bridges to the same hosted server, one per ecosystem:
There is a fourth way in that installs no package at all: mcpb/ packs the Node
bridge into a .mcpb desktop extension, a zip Claude desktop installs in one click.
It is the same bridge with BOWMARK_MCP_URL preset, not a separate implementation.
The npm package is scoped and the PyPI one is not, deliberately. npm moved to
@bowmark/mcp on 2026-08-05; PyPI cannot be scoped at all (PEP 752 standardises
hyphen-prefixed namespaces, and PyPI has no rename, alias or redirect), so
bowmark-mcp there is already the blessed form and is unchanged. The unscoped
npm name is not retired — node-compat/ publishes it as a package whose bin
re-execs the scoped one, because npm cannot be unpublished and npm deprecate
only warns. Every config in the wild keeps working; new ones should say
@bowmark/mcp.
Both bridges are verbatim pass-throughs: tool schemas, descriptions, and results come from the hosted server at runtime, so the bridges never lag the api and there is no logic here to audit beyond "forward the request." Pick whichever runtime your environment already has; they are interchangeable.
The one thing that cannot be lazy: instructions. Server-level instructions
ride on the bridge's OWN initialize, which happens before it has talked to the
api, so unlike tools they cannot be fetched per request. Each bridge does one
extra initialize at startup purely to read them and pass them on. That keeps the
hosted server the single source of truth; a hardcoded copy here would drift the
moment the api changed it and could only be fixed by a re-publish. If the fetch
fails the bridge starts without them, because a ranking hint is never worth
refusing to serve over.
{ "mcpServers": { "bowmark": { "command": "uvx", "args": ["bowmark-mcp"] } } }
{ "mcpServers": { "bowmark": { "command": "npx", "args": ["@bowmark/mcp"] } } }
If your host speaks streamable HTTP, skip the bridge entirely and connect to
https://api.bowmark.ai/mcp.
Env (both bridges): BOWMARK_API_KEY (required — create one at
bowmark.ai/dashboard/keys) and BOWMARK_MCP_URL
(target override).
Bowmark used to return navigation recipes for an agent to execute, through
ask and report_outcome. It now returns a callable function library and
runs the script itself. The tools are:
The bridges themselves are pass-throughs, so upgrading is not what moves you across — they list tools from the hosted server at call time, and 1.x already sees the new ones. The major bump marks the contract change honestly rather than letting it arrive silently. If a host cached the old schema and still calls a retired name, the server answers with a message saying what replaced it; it is never a silent failure against a dead endpoint.
This repo is a one-way mirror of packages/bowmark-mcp/ in Bowmark's private
monorepo — issues and PRs are welcome here and get carried upstream by the
maintainers.
Bowmark MCP for stdio hosts: web scraping and automation for AI agents. Live prices, quotes, bookings, anything behind a login. Starts with a free $10.
{ "mcpServers": { "bowmark-mcp": { "command": "npx", "args": [ "-y", "@bowmark/[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@bowmark/mcp se ejecuta localmente por stdio.
Última comprobación: 2026-11-14. Bowmark MCP for stdio hosts: web scraping and automation for AI agents. Live prices, quotes, bookings, anything behind a login. Starts with a free $10.