> ## Documentation Index
> Fetch the complete documentation index at: https://evolink.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Hermes MCP setup

> Native remote MCP configuration, browser authorization, tool verification, and troubleshooting

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](/docs/en/cli/hermes-agent).

## Connect remote MCP

For native tools, use **Streamable HTTP + OAuth** with this server URL:

```text theme={null}
https://mcp.evolink.ai/mcp
```

CLI installation is not required. Back up existing configuration, merge only EvoLink, and preserve other services. Choose command-based or manual registration.

<Steps>
  <Step title="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:

    ```yaml theme={null}
    mcp_servers:
      evolink:
        url: "https://mcp.evolink.ai/mcp"
        auth: oauth
        connect_timeout: 300
    ```
  </Step>

  <Step title="Authorize from a fresh terminal">
    ```bash theme={null}
    hermes mcp login evolink
    ```

    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.
  </Step>

  <Step title="Reload tools and verify for free">
    In the Hermes conversation, enter:

    ```text theme={null}
    /reload-mcp
    ```

    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.
  </Step>
</Steps>

For SSH callbacks, follow Hermes’s own configuration rather than EvoLink CLI flags. See [Hermes documentation](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp/).

After authorization, send this in the agent chat:

```text theme={null}
Use EvoLink to check my account balance and search available image models. Do not generate anything yet.
```

**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.

| Symptom | Action |
| - | - |
| URL added but no tools | Enable the connection, complete authorization, refresh, and check organization policy |
| 401 or authentication required | Reauthorize this MCP connection and retain original task IDs |
| 403 or tool denied | Check host permissions, account/Key status, and network errors |
| Timeout or lost response | Query and recover the original operation instead of regenerating |
| Link-only or gray preview | Open and deliver the original without automatically remaking it |

See [MCP costs, access, and troubleshooting](/docs/en/mcp/billing#faq). Read the [creation workflow](/docs/en/mcp/overview#workflows) before submitting; call shapes are in the [MCP tool reference](/docs/en/mcp/tools).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.