Chuyển đến nội dung chính
Both connect through standard MCP: Streamable HTTP, url plus header Authorization: Bearer. Syntax checked against the Hermes Agent MCP docs on 2026-11-20 (no version number is published on that page). Re-check if your Hermes version differs.

Hermes Agent

  1. Put the key in ~/.hermes/.env:
  2. Add to ~/.hermes/config.yaml:
    Hermes infers Streamable HTTP from url. Use underscores in the server name: tools are registered as mcp_<server>_<tool>, for example mcp_social_monitor_list_channels.
  3. Verify:
    In a running session run /reload-mcp to reload without restarting.
  4. Ask the agent to call list_channels.
The Hermes docs show ${VAR} expansion for some fields but do not state it for user-written headers. If hermes mcp test returns 401, write the literal value: Authorization: "Bearer smk_...".

GrokBot

Use the generic mcpServers block from Connect via MCP JSON in GrokBot’s MCP config. If your GrokBot build cannot send custom headers, use mcp-remote --header (same page) or the HTTP fallback.

Fallback: HTTP

No MCP client or no header support: HTTP bots.