Back to GigaRAG

Connect an agent

Give an AI tool access to your GigaRAG Workspace, so it can search, read and write your memos while it works.

Hermes Agent

Nous Research's self-improving agent, in the terminal, its desktop app and your chat apps.

Connect with the GigaRAG CLI

Hermes Agent keeps its settings somewhere a command cannot safely rewrite, so the CLI prints exactly what to enter instead. Signing in still happens in your browser, and no key is written into any config file.

npm install -g gigarag
gigarag login
gigarag connect hermes-agent

Paste what it prints, then restart Hermes Agent afterwards. Nothing here expires, and gigarag connect --remove takes GigaRAG back out of everything it touched.

Sign in with GigaRAG

Connect without a key: Hermes Agent opens your browser, you sign in to GigaRAG and pick this workspace.

  1. 1.

    Add GigaRAG with sign-in

    hermes mcp add gigarag --url https://mcp.gigarag.com/mcp --auth oauth
  2. 2.

    Start the sign-in

    On a machine without a browser, add --flow device and finish signing in on another device.

    hermes mcp login gigarag
  3. 3.

    Sign in with your GigaRAG account

    Your browser opens GigaRAG. Pick the workspace to share and approve. No key is stored in the app, and the connection does not expire.

Or paste a prompt

Paste this into Hermes Agent. It carries your agent key and tells the agent exactly what to change, so it sets the connection up itself.

Add GigaRAG as an MCP server. Append GIGARAG_API_KEY=<api-key> to ~/.hermes/.env, then merge into ~/.hermes/config.yaml:

mcp_servers:
  gigarag:
    url: "https://mcp.gigarag.com/mcp"
    headers:
      Authorization: "Bearer ${GIGARAG_API_KEY}"

Then run /reload-mcp. Don't repeat the key.

Or set it up by hand

  1. 1.

    Add your key to the Hermes env file

    ~/.hermes/.env
    GIGARAG_API_KEY=<api-key>
  2. 2.

    Add GigaRAG to your config

    Hermes reads the key from the env file when it connects, so the key never sits in the config.

    ~/.hermes/config.yaml
    mcp_servers:
  gigarag:
    url: "https://mcp.gigarag.com/mcp"
    headers:
      Authorization: "Bearer ${GIGARAG_API_KEY}"
    timeout: 120
  3. 3.

    Reload the servers from a Hermes chat

    /reload-mcp

Check it worked

Send this once it is connected. An answer drawn from your workspace means the connection is live.

List my GigaRAG buckets.

Written from the official docs: Hermes MCP, CLI commands