Updated 2026-10-01

Hermes (Nous Research)

Hermes by Nous Research reads MCP server configuration from ~/.hermes/config.yaml under the mcp_servers: key.

Install with the pinned CLI

CLI 0.2.14 has a matching installer for this client. Sign in first with npx -y lyrashield@0.2.14 login --oauth for local stdio. Review the planned changes before writing:

npx -y lyrashield@0.2.14 install hermes --dry-run

When the preview is correct, run the installer:

npx -y lyrashield@0.2.14 install hermes

The installer updates LyraShield's entry and preserves unrelated configuration. You can also use the manual snippet below. Restart or reload the client and complete a read-only authenticated call; an installed config entry alone does not prove client discovery.

Remote OAuth setup (recommended)

Add the remote configuration below to ~/.hermes/config.yaml, then run hermes mcp login lyrashield. Hermes completes PKCE OAuth in your browser and stores the token outside the configuration file.

Manual fallback: merge the following into ~/.hermes/config.yaml. Complete OAuth in the client after adding the server. No API key belongs in this config.

mcp_servers:
  lyrashield:
    url: "https://app.lyrashieldai.com/api/mcp"
    auth: "oauth"

npx -y lyrashield@0.2.14 install hermes

Important gotchas

• Hermes stores MCP entries under `mcp_servers` in ~/.hermes/config.yaml. It also supports `hermes mcp add` and `hermes mcp test <name>` from the CLI.
• Hermes resolves `${env:VAR}` and `${VAR}` in its YAML configuration. Prefer the environment reference over storing a key in config.yaml.

Local stdio alternative

Use the local server when the remote OAuth flow is unavailable:

Manual fallback: merge the following into ~/.hermes/config.yaml. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.

mcp_servers:
  lyrashield:
    command: "npx"
    args:
      - "-y"
      - "@lyrashield/mcp@0.2.12"
    env:
      LYRASHIELD_API_URL: "https://app.lyrashieldai.com"

npx -y lyrashield@0.2.14 install hermes

Important gotchas

• Hermes stores MCP entries under `mcp_servers` in ~/.hermes/config.yaml. It also supports `hermes mcp add` and `hermes mcp test <name>` from the CLI.
• Hermes resolves `${env:VAR}` and `${VAR}` in its YAML configuration. Prefer the environment reference over storing a key in config.yaml.

ACP for editor integrations

When using Hermes with editor integrations via the Agent Communication Protocol (ACP), the MCP tools registered in your profile are available to the connected editor. Follow your editor's ACP setup instructions to connect Hermes, then the LyraShield tools will surface automatically.

Verify the connection

Run hermes mcp test lyrashield after saving, then start Hermes and list available tools. The LyraShield MCP tools should appear in the tool registry.