Valerio d387669c13 refactor(create-webclaw): write the npx @webclaw/mcp config, drop binary download ... Aligns with the industry standard: Firecrawl, the official MCP reference servers, Exa, Brave, Apify, Bright Data, etc. all install their MCP via a single `npx -y <pkg>` config line — none use a create-* scaffolder for the MCP itself (create-* is a project-bootstrap convention). create-webclaw now auto-detects AI tools and writes the canonical `npx @webclaw/mcp` config into each, byte-identical to webclaw.io/docs and the MCP registries, so a scaffolded config can never diverge from a hand-written one. - buildMcpEntry + all writers emit {command:"npx", args:["-y","@webclaw/mcp"]} across every format (JSON, Continue array, OpenCode array, Codex TOML) - remove the entire binary-download machinery (getTarget/download/extract/cargo fallback, ~250 lines) — the @webclaw/mcp launcher handles that now - README: reflect the new behavior + show the one-block manual config - version 0.1.6 -> 0.1.7 Verified: correct npx config (with/without API key) across all formats; idempotent re-runs; zero binary-download code remains. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-22 11:34:01 +02:00
..
create-webclaw	refactor(create-webclaw): write the npx @webclaw/mcp config, drop binary download	2026-07-22 11:34:01 +02:00
webclaw-mcp	fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing	2026-07-22 08:53:29 +02:00