Skip to main content
This page covers native MCP in Hermes. The remote service uses Streamable HTTP and browser OAuth without requiring EvoLink CLI. For command and skill execution, use the separate CLI guide.

​
Connect remote MCP

For native tools, use Streamable HTTP + OAuth with this server URL:
CLI installation is not required. Back up existing configuration, merge only EvoLink, and preserve other services. Choose command-based or manual registration.
1

Merge server configuration

With an OAuth-capable Hermes version, back up and edit ~/.hermes/config.yaml. Merge into the existing mcp_servers mapping without repeating that top-level key. Use spaces for indentation:
2

Authorize from a fresh terminal

Sign in to EvoLink and approve in the browser while keeping the command running. Explicit login from a fresh terminal avoids the shorter automatic reload window after editing a running session’s configuration.
3

Reload tools and verify for free

In the Hermes conversation, enter:
Alternatively, open a new session and send the prompt below. Check that EvoLink tools are enabled; listing tools alone does not establish authorization for calls.
For SSH callbacks, follow Hermes’s own configuration rather than EvoLink CLI flags. See Hermes documentation. After authorization, send this in the agent chat:
Success: actual check_balance and search_models calls return results. Verify these tools in the actual MCP connection.

​
Updates, disconnection, and troubleshooting

EvoLink updates the hosted MCP server. Refresh the actual client session after configuration changes. Reauthorize through that client’s OAuth action when needed. Disable, sign out, or remove EvoLink in host MCP settings to disconnect; retain other servers. See MCP costs, access, and troubleshooting. Read the creation workflow before submitting; call shapes are in the MCP tool reference.