wigolo
Searches, fetches, crawls, extracts, caches, and researches the web through an authenticated remote MCP endpoint.
What it provides
Connect an existing HTTPS deployment, with a scoped token where the service requires one. Heavy jobs stay on that service instead of using bot memory.
Connection requirements
Deploy wigolo’s HTTP server outside the bot, publish /mcp through HTTPS, keep Bearer selected, and paste the remote-access token below. wigolo requires bearer authentication whenever it binds beyond loopback. Its Node 20+ engine needs about 1.5 GB of disk for the browser and local models, so keep that runtime and its data on the external host.
- Protocol
- Streamable HTTP MCP
- Endpoint
https://wigolo.example.com/mcp- Authentication
- bearer
mcp call search {"query":"OpenClaw MCP","max_results":5}mcp call fetch {"url":"https://example.com"}Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.