Skip to content

SPREVA opens soon.

Join the waitlist and we'll email you once, when your account is ready.

No newsletter. Just one email when SPREVA opens.

AI Agents

Hermes Agent

Nous Research's open-source agent, which keeps what it learns as skills.

Connects with
Sign in, API key, Skill
Connector
SPREVA
Plans
Free and open source. You bring your own model provider.

Before you start

  • Hermes Agent installed.
  • An API key, created in SPREVA under Developer, then API keys.

Set it up

  1. 1

    Add your SPREVA API key to Hermes's secrets file:

    ~/.hermes/.env
    SPREVA_API_KEY=POST_API_KEY_...
  2. 2

    Add SPREVA under mcp_servers in Hermes's configuration:

    ~/.hermes/config.yaml
    mcp_servers:
      spreva:
        url: "https://dev-app.spreva.ai/api/mcp"
        headers:
          Authorization: "Bearer ${SPREVA_API_KEY}"
  3. 3

    In a Hermes session, run /reload-mcp, or restart Hermes.

  4. 4

    Check that Hermes reaches SPREVA:

    Terminal
    hermes mcp test spreva

Also works with

  • Connector URL and sign in

    Paste the connector URL into the app, sign in to SPREVA and click Allow. No key to keep safe.

    Terminal
    hermes mcp add spreva \
      --url https://dev-app.spreva.ai/api/mcp \
      --auth oauth
  • The CLI and the Agent Skill

    Install the spreva command line and its Agent Skill, for agents that work in a terminal.

    Terminal
    export SPREVA_API_KEY=POST_API_KEY_...
    npx -y @spreva/cli skill install --target hermes

Check it works

Start a new conversation and ask:

Ask your agent
What's going out this week on SPREVA?

Hermes Agent calls SPREVA's overview tool and answers with the workspace's time zone, what goes out next and anything that needs attention. The first time, Hermes Agent may ask you to allow the tool.

Good to know

  • For the Agent Skill, add SPREVA_API_KEY to terminal.env_passthrough in ~/.hermes/config.yaml. Hermes keeps secrets out of the commands it runs unless they are listed there.

Troubleshooting

Hermes refuses to connect to SPREVA

Hermes doesn't connect while the key is empty. Check that ~/.hermes/.env has SPREVA_API_KEY, then run /reload-mcp.

Something else? Troubleshooting covers sign-in loops, plans, limits and time zones.