webclaw/smithery.yaml
Valerio 0678f0ba14 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

24 lines
770 B
YAML

# Smithery configuration — https://smithery.ai/docs/build/project-config
# webclaw MCP server: web extraction for AI agents with bot-protection bypass
startCommand:
type: stdio
configSchema:
type: object
properties:
apiKey:
type: string
description: >
webclaw API key from webclaw.io. Optional — the server works
locally without one. Set this for automatic fallback to the
webclaw cloud API when a site has bot protection or requires
JS rendering.
secret: true
commandFunction: |
(config) => ({
command: 'npx',
args: ['-y', '@webclaw/mcp'],
env: config.apiKey ? { WEBCLAW_API_KEY: config.apiKey } : {}
})
exampleConfig:
apiKey: wc_your_api_key_here