OpenClaw integration
On this page
OpenClaw can connect to Unfenced using its native MCP client. Use the remote server for readable web content and live-browser tools alongside your assistant's other capabilities.
Before you start
Use an OpenClaw release with the native openclaw mcp registry commands and an Unfenced account. If your setup runs inside NemoClaw, follow the NemoClaw guide so its sandbox policy and credentials are managed together.
Register and authorize the server
Run these commands on the host that runs OpenClaw:
openclaw mcp add unfenced \
--url https://unfenced.ai/api/mcp \
--transport streamable-http \
--auth oauth
openclaw mcp login unfenced
openclaw mcp doctor unfenced --probeComplete the Unfenced sign-in and approval flow opened by the login command. The probe checks whether the saved connection actually reaches the server and discovers tools. OAuth avoids putting an API key in your command or configuration.
OpenClaw stores native definitions under mcp.servers. An older mcporter registry is separate; adding a server there is not the same as registering a native MCP server.
Try your first fetch
Start a new agent conversation and ask:
Use the Unfenced MCP server's fetch_page tool to read https://example.com.
Return the page title, a short summary, and the source URL.Confirm the agent calls the Unfenced tool and describes Example Domain. OpenClaw may prefix the exposed tool name; the underlying tool is fetch_page.
If tools are missing
- Command unavailable: check your OpenClaw version and its native MCP documentation.
- Authorization failed: run
openclaw mcp login unfencedand complete the sign-in flow. - Probe succeeds but the agent has no tools: inspect its tool profile and policy. The
minimalprofile hides MCP tools, and abundle-mcpdeny rule disables them. - Configuration changed: begin a new turn or restart the runtime if hot reload is disabled.
What to try next
Use multi-source research or authenticated page reading. See OpenClaw's official MCP connection guide and registry commands for runtime-specific behavior.
Configuration reviewed: 2026-10-04. Check the connection in your client before relying on it.