Bots and personal agents

Hermes Agent

Hermes, the open-source agent from Nous Research, adds Hyperdex in one command. Answer yes when it asks whether the server needs authentication, and paste your key as the bearer token. Hermes stores the key in ~/.hermes/.env.

hermes mcp add hyperdex --url https://hyperdex.hypervect.com/mcp
hermes mcp test hyperdex

Run /reload-mcp in a running session to pick up changes. For a bot that talks to customers, add trust: untrusted under hyperdex so Hermes asks before every write.

OpenClaw

Add Hyperdex under mcp.servers in ~/.openclaw/openclaw.json, or in Settings, MCP. Keep the key in an environment variable rather than in the file, then check the connection.

{
  mcp: {
    servers: {
      hyperdex: {
        url: "https://hyperdex.hypervect.com/mcp",
        transport: "streamable-http",
        headers: { Authorization: "Bearer ${HYPERDEX_API_KEY}" }
      }
    }
  }
}

Use a current OpenClaw release: older versions had a security issue (CVE-2026-53840) that could forward custom headers to another site on a redirect.

Grok (xAI)

In the xAI API, add Hyperdex as a remote MCP tool and put your key in authorization. Hyperdex accepts the key with or without the word Bearer.

curl https://api.x.ai/v1/responses \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "grok-4.7",
    "input": "Which deals have gone quiet this month?",
    "tools": [{
      "type": "mcp",
      "server_label": "hyperdex",
      "server_url": "https://hyperdex.hypervect.com/mcp",
      "authorization": "hdx_your_key"
    }]
  }'

The Grok app also has custom connectors (grok.com, Connectors, New Connector, Custom). xAI does not document whether they accept an API key, so if no key option appears, use the API instead.

Mistral Le Chat

An admin opens Connectors, Add Connector, Custom MCP Connector, names it hyperdex, pastes https://hyperdex.hypervect.com/mcp and chooses HTTP Bearer Token with your key.

Perplexity

In the app, open Connectors, Add custom, Add MCP connector, Remote, paste https://hyperdex.hypervect.com/mcp, choose API Key authentication and Streamable HTTP. In an organisation an admin must first allow members to add connectors. In the Agent API, pass the key as the MCP tool’s authorization:

{
  "type": "mcp",
  "server_url": "https://hyperdex.hypervect.com/mcp",
  "authorization": "hdx_your_key"
}

Goose

Run goose configure, choose Add Extension, Remote Extension (Streamable HTTP), or add Hyperdex to ~/.config/goose/config.yaml:

extensions:
  hyperdex:
    name: Hyperdex
    type: streamable_http
    uri: https://hyperdex.hypervect.com/mcp
    headers:
      Authorization: "Bearer hdx_your_key"
    enabled: true
    timeout: 300