One-click deploys
The README has a deploy button for each hosted platform. Every button starts from the same public repository, so you can read exactly what gets deployed before you click.
Fly.io has no button, but the repository includes fly.toml:
fly launch --copy-configAfter you click
Section titled “After you click”- Set two secrets.
CALLER_TOKENis what your agents and the/adminconsole use.AGENT_TOKENis what worker nodes use to connect. Use long random values, for exampleopenssl rand -hex 24. - Open
/adminon your new hub and sign in with the caller token. - Connect your agent to
https://<your-hub>/mcp. See Connect an MCP client. - Add a worker if your hub has none built in. See Add worker nodes.
On Cloudflare, a hub with no workers still fetches through Cloudflare’s own network, but adding a worker at home gives you your own IP address and a headless browser for JavaScript pages.
Optional features to switch on
Section titled “Optional features to switch on”All of these are off until you configure them:
| Feature | What to set |
|---|---|
| Web search | SERPER_API_KEY, BRAVE_API_KEY or TAVILY_API_KEY, or SEARXNG_URL for a free self-hosted option |
| Stored artifacts and crawl history | The ARTIFACTS R2 bucket and META D1 database in hub/wrangler.toml |
| Full-text search over what you’ve collected | The SEARCH D1 database |
| Signed requests (Web Bot Auth) | BOT_SIGNING_PRIVATE_KEY, from edgefetch keygen-bot-auth |
| Tracing | OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_HEADERS |
| Heavy single-page apps | CRAWL4AI_API_URL, or FIRECRAWL_API_URL and FIRECRAWL_API_KEY, as a fallback after robots.txt passes |
