Local Hermes on your system — the intelli-verse-x way
When to use this skill
- Fresh machine that needs Hermes with all org services wired.
- An existing local install is missing MCP servers, skills, or the
self-hosted Firecrawl and you need to bring it up to org parity.
- Someone asks what a "correct" local
~/.hermes looks like here.
One-shot install (recommended)
curl -fsSL https://raw.githubusercontent.com/intelli-verse-x/hermes-deployment/main/scripts/install-local.sh | bash
That script (repo: intelli-verse-x/hermes-deployment):
- Installs hermes-agent via the official NousResearch one-liner if missing.
- Seeds
~/.hermes/config.yaml + AGENTS.md from config/ (diffs, never
clobbers an existing file).
- Symlinks the org skill bundle to
~/.hermes/skills/ivx-deployment
(so git pull in hermes-deployment updates skills in place).
- Checks prerequisites:
gt, bd, firecrawl, npx, uvx, plus
git/gh/kubectl for coding-loop and deploy work.
- Tells you which env keys are still empty.
Required env (~/.hermes/.env)
| Key |
Value / where to get it |
OPENAI_API_KEY |
LiteLLM virtual key (litellm.intelli-verse-x.ai; ask infra or mint via litellm/scripts/mint-role-keys.sh) |
ADMIN_MCP_TOKEN |
Scoped to your email's access grant. Super admins: kubectl get secret admin-mcp-token -n aicart -o jsonpath='{.data.ADMIN_MCP_TOKEN}' | base64 -d. Everyone else: ask a super admin |
FIRECRAWL_API_URL |
https://firecrawl.intelli-verse-x.ai (self-hosted on EKS) |
FIRECRAWL_API_KEY |
any non-empty value, e.g. self-hosted (instance is unauthenticated) |
GH_TOKEN |
your GitHub PAT if you want PR/issue workflows |
Per-service MCP tokens (NOTIFUSE_MCP_TOKEN, TWENTY_MCP_TOKEN, …) are
optional — leave empty to reach those services through the admin-mcp
gateway instead. See config/.env.example in hermes-deployment for the
full list and where each token comes from.
What the seeded config gives you
- Model routing through the org LiteLLM proxy
(
https://litellm.intelli-verse-x.ai/v1) — one shared budget envelope.
- MCP servers:
admin-mcp gateway (7 meta-tools fanning out to every
admin portal tile), 13 direct EKS MCPs (notifuse, whatsapp, fonoster,
postiz, twenty, chatwoot, telnyx, nakama-console, grafana, documenso,
intelliverse-mcp, agent-mcp, open-seo), firecrawl, gastown, n8n,
content-factory.
- Skills: org bundles from hermes-deployment, hermes-agent fork
(
ivx-* + ivx-mcp-* catalog), nakama .agents/skills, and curated
upstream packs. Same SKILL.md folders work in Cursor, Claude Code,
Codex, and Goose.
Verify the install
hermes doctor # config + connectivity checks
hermes mcp list # every server above should show connected/ready
hermes chat -q "search the web for intelliverse quizverse and cite the tool used"
hermes doctor failures to check first: empty OPENAI_API_KEY (LiteLLM),
ADMIN_MCP_TOKEN missing (admin-mcp shows unauthorized), VPN required for
cluster-local-only endpoints.
Desktop app (IX Agency)
The org's rebranded Hermes Desktop lives in intelli-verse-x/hermes-agent
branch feat/ix-agency; installers publish to the S3 feed
(intelliverse-x-desktop/ix-agency/) and auto-update in place. On portal
login (admin.intelli-verse-x.ai email OTP) the app auto-attaches the MCP
directory, dynamic connectors, and org skills — no manual wiring.
Updating
hermes update # hermes itself
git -C ~/dev/hermes-deployment pull # org config + skills (symlinked)
Related
- Delegating work to the cloud workers instead of running locally:
ivx-hermes-cloud-delegate.
- What each MCP/tool does and how to call it:
ivx-mcp-directory and the
ivx-mcp-* skills.
1---2name: ivx-hermes-local3description: Install, configure, and run Hermes Agent locally on a laptop/workstation with the full intelli-verse-x wiring — LiteLLM gateway, admin-mcp, self-hosted Firecrawl, org skills, and the IX Agency desktop app. Use when someone asks "how do I get Hermes on my machine", when bootstrapping a new employee system, or when a local install is missing MCPs/tools/skills that the org supports.4---56# Local Hermes on your system — the intelli-verse-x way78## When to use this skill910- Fresh machine that needs Hermes with all org services wired.11- An existing local install is missing MCP servers, skills, or the12 self-hosted Firecrawl and you need to bring it up to org parity.13- Someone asks what a "correct" local `~/.hermes` looks like here.1415## One-shot install (recommended)1617```bash18curl -fsSL https://raw.githubusercontent.com/intelli-verse-x/hermes-deployment/main/scripts/install-local.sh | bash19```2021That script (repo: `intelli-verse-x/hermes-deployment`):22231. Installs hermes-agent via the official NousResearch one-liner if missing.242. Seeds `~/.hermes/config.yaml` + `AGENTS.md` from `config/` (diffs, never25 clobbers an existing file).263. Symlinks the org skill bundle to `~/.hermes/skills/ivx-deployment`27 (so `git pull` in hermes-deployment updates skills in place).284. Checks prerequisites: `gt`, `bd`, `firecrawl`, `npx`, `uvx`, plus29 git/gh/kubectl for coding-loop and deploy work.305. Tells you which env keys are still empty.3132## Required env (`~/.hermes/.env`)3334| Key | Value / where to get it |35|-----|------------------------|36| `OPENAI_API_KEY` | LiteLLM virtual key (litellm.intelli-verse-x.ai; ask infra or mint via `litellm/scripts/mint-role-keys.sh`) |37| `ADMIN_MCP_TOKEN` | Scoped to your email's access grant. Super admins: `kubectl get secret admin-mcp-token -n aicart -o jsonpath='{.data.ADMIN_MCP_TOKEN}' \| base64 -d`. Everyone else: ask a super admin |38| `FIRECRAWL_API_URL` | `https://firecrawl.intelli-verse-x.ai` (self-hosted on EKS) |39| `FIRECRAWL_API_KEY` | any non-empty value, e.g. `self-hosted` (instance is unauthenticated) |40| `GH_TOKEN` | your GitHub PAT if you want PR/issue workflows |4142Per-service MCP tokens (`NOTIFUSE_MCP_TOKEN`, `TWENTY_MCP_TOKEN`, …) are43optional — leave empty to reach those services through the admin-mcp44gateway instead. See `config/.env.example` in hermes-deployment for the45full list and where each token comes from.4647## What the seeded config gives you4849- **Model routing** through the org LiteLLM proxy50 (`https://litellm.intelli-verse-x.ai/v1`) — one shared budget envelope.51- **MCP servers**: `admin-mcp` gateway (7 meta-tools fanning out to every52 admin portal tile), 13 direct EKS MCPs (notifuse, whatsapp, fonoster,53 postiz, twenty, chatwoot, telnyx, nakama-console, grafana, documenso,54 intelliverse-mcp, agent-mcp, open-seo), `firecrawl`, `gastown`, `n8n`,55 content-factory.56- **Skills**: org bundles from hermes-deployment, hermes-agent fork57 (`ivx-*` + `ivx-mcp-*` catalog), nakama `.agents/skills`, and curated58 upstream packs. Same SKILL.md folders work in Cursor, Claude Code,59 Codex, and Goose.6061## Verify the install6263```bash64hermes doctor # config + connectivity checks65hermes mcp list # every server above should show connected/ready66hermes chat -q "search the web for intelliverse quizverse and cite the tool used"67```6869`hermes doctor` failures to check first: empty `OPENAI_API_KEY` (LiteLLM),70`ADMIN_MCP_TOKEN` missing (admin-mcp shows unauthorized), VPN required for71cluster-local-only endpoints.7273## Desktop app (IX Agency)7475The org's rebranded Hermes Desktop lives in `intelli-verse-x/hermes-agent`76branch `feat/ix-agency`; installers publish to the S3 feed77(`intelliverse-x-desktop/ix-agency/`) and auto-update in place. On portal78login (admin.intelli-verse-x.ai email OTP) the app auto-attaches the MCP79directory, dynamic connectors, and org skills — no manual wiring.8081## Updating8283```bash84hermes update # hermes itself85git -C ~/dev/hermes-deployment pull # org config + skills (symlinked)86```8788## Related8990- Delegating work to the cloud workers instead of running locally:91 `ivx-hermes-cloud-delegate`.92- What each MCP/tool does and how to call it: `ivx-mcp-directory` and the93 `ivx-mcp-*` skills.
intelli-verse-x