Hermes

https://api.eksis.io/mcp

Connect the eksis MCP server to Hermes on this computer.

Server URL: https://api.eksis.io/mcp
Setup guide: https://docs.eksis.io/en/mcp/clients/hermes

Use OAuth sign-in. Follow the API key steps only if I give you a key that starts with eksis_sk_. Then use my key wherever the steps show eksis_sk_..., or set it as EKSIS_API_KEY where they read that variable.

OAuth:
```bash
hermes mcp add eksis --url https://api.eksis.io/mcp --auth oauth
```

API key:
```bash
hermes mcp add eksis --url https://api.eksis.io/mcp --auth header
```

From the setup guide:
One command adds the server. With `--auth oauth`, Hermes registers itself with eksis and opens your browser so you can pick the workspace and the permissions it may use, then lists the eksis tools and asks which ones to enable. The token is kept in `~/.hermes/mcp-tokens/`, and `hermes mcp login eksis` signs in again. With `--auth header`, Hermes asks for the API key and saves it to `~/.hermes/.env` as `MCP_EKSIS_API_KEY`, so the key never sits in `~/.hermes/config.yaml`. Either way the command writes an `eksis` entry under `mcp_servers` in that file. `hermes mcp test eksis` checks the connection, and `/reload-mcp` picks up the change in a running session.

Rules:
- If Hermes already has a server named eksis, show me its entry and ask before you change it.
- Never put an API key in a file that is committed to git. Keep it in an environment variable or the client's own secret store, as the steps show.
- If a command asks a question interactively, show me the question and wait for my answer.
- When eksis opens a sign-in page in the browser, stop and ask me to pick the workspace and approve it. Do not approve it for me.

When you are done, check the connection and list the eksis tools Hermes can see. If it fails, show me the error.