Rename binaries or name in config

[LuisPeregrina]

Most agents and llms actually resolve webclaw/webclaw-mcp as kuroko1t/webclaw (npmjs). Even if told that this project is different.

Maybe we can use webclaw-io-mcp, or something of the sort to diferenciate with this project?

[0xMassi]

Thanks for flagging this, you're right. The webclaw-mcp name on npm belongs to a different project (kuroko1t/webclaw, a Chrome browser agent), so any agent that guesses npx webclaw-mcp lands on the wrong package.

I'd rather not rename the binary. That breaks everyone who already has webclaw-mcp in their config, and npx webclaw-io-mcp would just 404. Instead I'll publish under the scope I own, @webclaw/mcp, so there's a correct, unambiguous target (npx @webclaw/mcp) and update the docs to lead with it. Existing setups stay untouched.

One thing so I can reproduce it cleanly: which agent/client were you using, and what command did it run when it grabbed the wrong package?

[LuisPeregrina]

This was under opencode, don't remember the agent used, but it refused to use webclaw saying it was overkill. I have fixed this by naming the mcp as "webclaw-io" and stopped having this issue:

{
  "$schema": "https://opencode.ai/config.json",

  "mcp": {
    "webclaw-io": {
      "type": "local",
      "command": [
        "webclaw-mcp"
      ]
    }
  }
}