Skip to content
unfenced.ai

Hermes Agent integration

On this page

Nous Research's Hermes Agent can use Unfenced through remote MCP. The connection adds web-reading and live-browser tools to Hermes without running an Unfenced browser locally.

Before you start

Install Hermes Agent with MCP support and sign in to Unfenced to create your agent’s API key. If Hermes runs in a NemoClaw sandbox, use the NemoClaw integration instead of copying a key into the sandbox.

Store the key privately

Edit ~/.hermes/.env and add this line, replacing the placeholder with your Unfenced key:

Example
UNFENCED_TOKEN=YOUR_API_KEY

Keep this file private and out of Git. If you use a named Hermes profile, store the variable in that profile's secret scope instead.

Add the remote server

Edit ~/.hermes/config.yaml. Merge this entry into your existing mcp_servers mapping:

YAML
mcp_servers:
  unfenced:
    url: "https://unfenced.ai/api/mcp"
    headers:
      Authorization: "Bearer ${UNFENCED_TOKEN}"

Hermes uses Streamable HTTP for a URL-based server by default. It resolves the variable from the active profile's secrets or environment, so the configuration can contain the placeholder rather than the key.

Start a fresh conversation:

Terminal
hermes chat

Try your first fetch

Ask Hermes:

Agent prompt
Use the Unfenced MCP server's fetch_page tool to read https://example.com.
Give me a short summary and cite the source URL.

Check that a tool call returned Example Domain content. Hermes may add a server prefix to the tool name.

If it does not connect

  • Missing-variable error: put UNFENCED_TOKEN in the active profile's secret scope and reconnect.
  • Unauthorized: verify that the key is active and has no accidental spaces.
  • No tools: check YAML indentation, confirm the server is enabled, and start a new chat.
  • Tools were filtered out: review the server's tools configuration before changing account permissions.

What to try next

Use multi-URL research or authenticated page reading. See the official Hermes MCP guide and configuration reference.

Configuration reviewed: 2026-10-04. Check the connection in your client before relying on it.

Request accessSign in