+ NanoClaw + Wayfern
NanoClaw runs each agent group in its own container, with only the mounts you give it. A container that reads the live web meets the same bot blocks as any script.
Add Wayfern to one agent group. The container calls the Wayfern tools over HTTPS, and the OneCLI vault holds the token outside the container.
! Note:NanoClaw does not document MCP OAuth, or how OneCLI sends the token. Check that the first call reaches Wayfern with an Authorization: Bearer header.

container · group home no host mount
@Andy what does the ferry page say about tomorrow's sailings?
wayfern · scrape_pageislandferries.dev/timetable
markdown · credits_charged: 1
Tomorrow: 07:10, 09:40, 13:15 and 18:30. The 21:00 sailing is cancelled.
POSTapi.wayfern.com/mcp
200page text, back to the container
Setup
Each agent group gets its own servers. Add Wayfern only to the groups that need it.
Skip this when it is installed.
bash
git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2
cd nanoclaw-v2 && bash nanoclaw.shDo not edit groups/<folder>/container.json. NanoClaw writes it again at each start.
bash
ncl groups config add-mcp-server --id <group-id> --name wayfern --url https://api.wayfern.com/mcp
ncl groups restart --id <group-id>Create a token with the mcp scope on the Tokens page. set-secrets replaces the whole list, so keep the current IDs in it.
bash
onecli secrets create --name Wayfern --type api_key --value "$WAYFERN_API_TOKEN" --host-pattern api.wayfern.com
onecli agents set-secrets --id "$AGENT_ID" --secret-ids "<current ids>,<new id>"prompt
@Andy what does the ferry company's page say about tomorrow's sailings?Route
The container reaches api.wayfern.com over HTTPS and needs no host mount. NanoClaw does not document MCP OAuth, so the token comes from the OneCLI vault.
wf_ token from the OneCLI vault, matched to api.wayfern.com.Example tasks
01
“@Andy what does the ferry company's page say about tomorrow's sailings?”
scrape_page at 1 credit.
02
prompt
ncl tasks create --group <id> --recurrence "0 9 * * 1-5" \
--prompt "Read the city's road works page with Wayfern. Message me on Signal only when a new closure is listed." One scrape_page call each weekday, 1 credit.
03
“@Andy search for news about the port strike from today and give me three lines.”
search_web bills 2 credits for each provider page.
04
“@Andy send me a screenshot of the weather service's warning map.”
capture_screenshot returns an image URL for 5 credits.
Tools
The same tools on every route, at the REST API rates. Every result reports credits_charged.
add_mcp_server, an admin approves it from a card in a direct message.--script gate.Sign in once and the tools appear. Tool calls use the credits of your Wayfern plan, at the same rates as the API.