apunkt/webclaw
1
0
Fork 0
mirror of https://github.com/0xMassi/webclaw.git synced 2026-07-25 07:41:01 +02:00
Code Issues Projects Releases Packages Wiki Activity
webclaw/packages/webclaw-mcp/package.json

40 lines
899 B
JSON
Raw Permalink Normal View History

feat(mcp): add @webclaw/mcp zero-install launcher as the canonical MCP command `npx -y @webclaw/mcp` downloads the prebuilt webclaw-mcp binary (verified against the release SHA256SUMS), caches it, and runs it as an MCP stdio server. This makes webclaw introspectable in MCP registries (Glama/Smithery/MCP registry) and installable in any MCP client with no Rust build. - packages/webclaw-mcp: zero-dep launcher (.mjs) + package.json + README - README/CLAUDE/examples/smithery: mcpServers config -> npx -y @webclaw/mcp - registry: point the MCP-registry entry (server.json) at @webclaw/mcp, the real stdio server, instead of create-webclaw (a scaffolder); drop create-webclaw's mcpName claim so ownership isn't duplicated - CHANGELOG: unreleased entry create-webclaw stays as the auto-detect installer. .mcp.json is intentionally left pointing at the local install path until @webclaw/mcp is published to npm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 18:14:30 +02:00
{
"name": "@webclaw/mcp",
fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing The published bin was named `webclaw-mcp`, which npx shadows with any existing `webclaw-mcp` on PATH (Homebrew/cargo/create-webclaw) — so `npx @webclaw/mcp` silently ran a stale binary instead of the launcher, for exactly our existing CLI users. Rename the bin to the unique `webclaw-mcp-launcher`; `npx @webclaw/mcp` still resolves the single bin. Verified end-to-end: with a stale webclaw-mcp on PATH, npx now runs the launcher and returns 14 tools. - bin: webclaw-mcp -> webclaw-mcp-launcher; version 0.6.15 -> 0.6.16 - mark webclaw-mcp.mjs executable - release.yml: version the launcher INDEPENDENTLY of the core release (a launcher-only fix must ship without a core bump) — publish the next patch above the current npm version and pin RELEASE_TAG to the release tag - server.json: sync to 0.6.16 Published + deprecated 0.6.15 (bin collision); 0.6.16 is the first good release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-22 08:53:29 +02:00
"version": "0.6.16",
feat(mcp): add @webclaw/mcp zero-install launcher as the canonical MCP command `npx -y @webclaw/mcp` downloads the prebuilt webclaw-mcp binary (verified against the release SHA256SUMS), caches it, and runs it as an MCP stdio server. This makes webclaw introspectable in MCP registries (Glama/Smithery/MCP registry) and installable in any MCP client with no Rust build. - packages/webclaw-mcp: zero-dep launcher (.mjs) + package.json + README - README/CLAUDE/examples/smithery: mcpServers config -> npx -y @webclaw/mcp - registry: point the MCP-registry entry (server.json) at @webclaw/mcp, the real stdio server, instead of create-webclaw (a scaffolder); drop create-webclaw's mcpName claim so ownership isn't duplicated - CHANGELOG: unreleased entry create-webclaw stays as the auto-detect installer. .mcp.json is intentionally left pointing at the local install path until @webclaw/mcp is published to npm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 18:14:30 +02:00
"description": "Zero-install launcher for the webclaw MCP server: web extraction and anti-bot access for AI agents. Runs `npx @webclaw/mcp`.",
"type": "module",
"bin": {
fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing The published bin was named `webclaw-mcp`, which npx shadows with any existing `webclaw-mcp` on PATH (Homebrew/cargo/create-webclaw) — so `npx @webclaw/mcp` silently ran a stale binary instead of the launcher, for exactly our existing CLI users. Rename the bin to the unique `webclaw-mcp-launcher`; `npx @webclaw/mcp` still resolves the single bin. Verified end-to-end: with a stale webclaw-mcp on PATH, npx now runs the launcher and returns 14 tools. - bin: webclaw-mcp -> webclaw-mcp-launcher; version 0.6.15 -> 0.6.16 - mark webclaw-mcp.mjs executable - release.yml: version the launcher INDEPENDENTLY of the core release (a launcher-only fix must ship without a core bump) — publish the next patch above the current npm version and pin RELEASE_TAG to the release tag - server.json: sync to 0.6.16 Published + deprecated 0.6.15 (bin collision); 0.6.16 is the first good release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-22 08:53:29 +02:00
"webclaw-mcp-launcher": "./webclaw-mcp.mjs"
feat(mcp): add @webclaw/mcp zero-install launcher as the canonical MCP command `npx -y @webclaw/mcp` downloads the prebuilt webclaw-mcp binary (verified against the release SHA256SUMS), caches it, and runs it as an MCP stdio server. This makes webclaw introspectable in MCP registries (Glama/Smithery/MCP registry) and installable in any MCP client with no Rust build. - packages/webclaw-mcp: zero-dep launcher (.mjs) + package.json + README - README/CLAUDE/examples/smithery: mcpServers config -> npx -y @webclaw/mcp - registry: point the MCP-registry entry (server.json) at @webclaw/mcp, the real stdio server, instead of create-webclaw (a scaffolder); drop create-webclaw's mcpName claim so ownership isn't duplicated - CHANGELOG: unreleased entry create-webclaw stays as the auto-detect installer. .mcp.json is intentionally left pointing at the local install path until @webclaw/mcp is published to npm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-21 18:14:30 +02:00
},
"mcpName": "io.github.0xMassi/webclaw",
"files": [
"webclaw-mcp.mjs",
"README.md"
],
"engines": {
"node": ">=18"
},
"license": "AGPL-3.0-only",
"author": "0xMassi",
"homepage": "https://webclaw.io",
"repository": {
"type": "git",
"url": "git+https://github.com/0xMassi/webclaw.git",
"directory": "packages/webclaw-mcp"
},
"bugs": {
"url": "https://github.com/0xMassi/webclaw/issues"
},
"keywords": [
"mcp",
"model-context-protocol",
"webclaw",
"web-scraping",
"web-extraction",
"ai-agents",
"cloudflare",
"anti-bot",
"llm"
]
}
Reference in a new issue Copy permalink