How to Connect Hermes Agent to MCP with Arcade.dev

Sign up<br>Dashboard<br>Book a demo

Sign up<br>Dashboard

Book a demo

How to Connect Hermes Agent to MCP with Arcade.dev

Manveer Chawla<br>JUNE 27, 2026<br>8 MIN READ<br>TUTORIALS

For developers running Nous Research’s Hermes Agent, connecting to a remote Model Context Protocol (MCP) server is straightforward. But as you add more services, you run into real problems: configuration sprawl, credential management, and raw API wrappers that cause the language model to hallucinate parameters and burn tokens.

Arcade.dev’s MCP gateway gives your Hermes Agent access to thousands of agent-optimized tools through a single endpoint, with downstream credentials vaulted away from the agent process and native OAuth for gateway authentication.

Scope note: One person, one Hermes profile, one gateway process. A shared multi-user service needs per-user MCP connections and token storage, plus an appropriate isolation boundary (containers or OS-level separation, since Hermes profiles are not sandboxes). Arcade User Sources can provide external identity for production agents, but do not add per-user MCP isolation to Hermes by themselves. That architecture is a separate problem.

TL;DR

Install MCP support (included in the standard installer; from source: uv pip install -e ".[mcp]").

Point Hermes at your Arcade MCP gateway using auth: oauth in ~/.hermes/config.yaml. Do not put a static ARCADE_API_KEY in the config; Hermes’s native OAuth flow establishes a user-bound session in Arcade.

Authorize each required tool or provider scope set through Arcade’s tools.authorize API before running tool calls that need them. Arcade vaults the tokens so they never reach the language model.

Restrict tool exposure with tools.include / tools.exclude for least privilege.

How to connect Hermes Agent to an MCP server (quick start)

Before connecting to Arcade, make sure your base Hermes Agent installation supports the Model Context Protocol. The standard installer includes MCP support by default. If you’re working from source or managing a custom environment, install the MCP extras from the repository root:

Install MCP support (from source)

uv pip install -e ".[mcp]"<br>Add an MCP server to ~/.hermes/config.yaml

Once installed, Hermes routes connections through the mcp_servers block in config.yaml. For a basic test against a standard HTTP MCP server, define the connection and inject a static Bearer token:

mcp_servers:<br>remote_test_api:<br>url: "https://mcp.internal.example.com"<br>headers:<br>Authorization: "Bearer ${REMOTE_TEST_API_KEY}"<br>This pattern is fine for a single developer hitting an internal test server they control. For remote servers that support OAuth, prefer Hermes’s native OAuth flow instead of static tokens.

Authenticate with Hermes’s native OAuth flow

The recommended way to connect Hermes to OAuth-protected remote MCP servers, including Arcade, is through its native OAuth 2.1 support. Set auth: oauth in the configuration block. When configured, Hermes handles dynamic client registration, prints an authorization URL to the terminal, opens your browser, and waits for the callback on a local loopback port.

mcp_servers:<br>my_server:<br>url: "https://example.com/mcp"<br>auth: oauth<br>Authenticate and reload tools

After saving an OAuth configuration, run hermes mcp login from a fresh terminal. This provides enough time to complete browser authentication (five minutes, compared to the 30-second window during automatic config reload). Once authenticated, start or restart Hermes. Use /reload-mcp in the chat interface when you need to refresh the registered tools after later configuration changes.

Verify the tools loaded successfully by running:

hermes mcp test server><br>Why connect Hermes to Arcade

You could wire Hermes to each service individually, one MCP server for Gmail, another for Slack, another for your CRM. That works until you’re managing a dozen config blocks, each with its own credentials, timeouts, and failure modes. Arcade solves several problems at once.

One endpoint instead of many

The Arcade MCP Gateway gives your Hermes Agent access to thousands of tools through a single URL. Instead of managing separate server connections and keeping track of which service lives where, your Hermes Agent talks to one gateway. Arcade handles routing and tool execution behind it.

Agent-optimized tools reduce hallucinations and token cost

Raw API wrappers hurt agent performance because they’re built for deterministic software, not probabilistic language models.

When an agent receives a raw API definition, it frequently hallucinates required parameters, enters retry loops on malformed JSON payloads, and burns tokens trying to correct its own errors. Arcade’s tools are designed at the intent level, translating natural language into precise API calls. In published benchmarks, this approach has cut response token usage substantially compared to raw API passthrough, while also lowering parameter hallucination...