Connect your AI

Connect Hermes Agent to your search.

Hermes is configured by editing YAML rather than by a command, so both routes are "put this block in the file, then run one command."

These steps follow Hermes Agent's own documentation. We have not connected Hermes to SoloSearcher ourselves, so if a screen or a flag does not match what you see, trust the client — and tell us, so we can fix this page.

Hermes runs the whole sign-in flow itself, including refreshing the token later. No key to create.

Add SoloSearcher to ~/.hermes/config.yaml:

mcp_servers:
  solosearcher:
    url: "https://app.solosearcher.com/mcp"
    auth: oauth

Start the sign-in flow:
```
hermes mcp login solosearcher
```
Your browser opens SoloSearcher. Sign in, then choose what Hermes is allowed to do — read-only or read-and-write.
Confirm the server answers:
```
hermes mcp test solosearcher
```

The token is kept in ~/.hermes/mcp-tokens/solosearcher.json. Inside a running session, /reload-mcp picks up config changes.

API key #

For a machine that cannot open a browser — a server, a container, a headless box.

Create an API key in Settings → Connections → API keys and copy it right away — it is shown once.
Put it in ~/.hermes/.env, so the config itself never holds the secret:
```
SOLOSEARCHER_API_KEY=your-key-here
```

Point Hermes at the server in ~/.hermes/config.yaml, referencing that variable:

mcp_servers:
  solosearcher:
    url: "https://app.solosearcher.com/mcp"
    headers:
      Authorization: "Bearer ${SOLOSEARCHER_API_KEY}"

Confirm the server answers:
```
hermes mcp test solosearcher
```

Hermes resolves ${VAR} when it connects, so the key stays out of config.yaml. Its tools arrive named mcp_solosearcher_<tool>.

Choose what Hermes can do #

Every connection is scoped when you approve it. Read-only lets Hermes search and read your companies, notes, contacts, and financials. Read-and-write also lets it save its work — finished reports, notes, and updates land on the company record instead of staying in the chat.

A read-only connection can still run any skill; it returns the analysis to you in the conversation rather than storing it. You can revoke access at any time, and every request is recorded in the product audit trail.

First thing to try #

One prerequisite: skills stay locked until you've saved a Buyer Profile — your display name plus at least one of your background, your thesis, or a target range. Two minutes, once. See Buyer Profile for what it unlocks and exactly how to set it. Skills are scored against your criteria, which is why the profile comes first.

Then ask Hermes for something you actually want to know:

Summarize my pipeline by status, then draft outreach for one company I haven't contacted.

With read-and-write access, the result of a skill run saves onto the company record as a report — run it again later and you get a new version next to the old one. On a read-only connection the analysis comes back in the conversation instead.

Troubleshooting #

Arriving with a JSON mcpServers block from another client? Hermes reads mcp_servers from YAML. It can migrate a Claude config with hermes import-agent claude-code, but that path is stdio-shaped — SoloSearcher is a remote HTTP server, so the url: form above is the one that works.

Connect Hermes Agent to your search.

Browser sign-in #

API key #

Choose what Hermes can do #

First thing to try #

Troubleshooting #

Read more #