HaloPSA and Servosity in Hermes

Hermes is Nous Research’s autonomous research agent. It’s one of two skill-native agents (besides Claude) that read MSP Skills’ SKILL.md directly and speak MCP - so you have two install paths.

What you need

Step 1 - Install MSP Skills binaries

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.sh)
bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/servosity/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/halopsa/install.ps1 | iex
iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/servosity/install.ps1 | iex

Path A - install as a Skill (uses the cli-printing-press template)

From the Hermes CLI:

hermes skills install Servosity/msp-skills/skills/halopsa --force
hermes skills install Servosity/msp-skills/skills/servosity --force

Or inside a Hermes chat session:

/skills install Servosity/msp-skills/skills/halopsa --force

Path B - register as an MCP server (most reliable)

Hermes speaks MCP natively, so it can use the binaries directly:

hermes mcp add halopsa -- halopsa-mcp
hermes mcp add servosity -- servosity-mcp

Set the same env vars the CLI needs (HALOPSA_TENANT / HALOPSA_CLIENT_ID / HALOPSA_CLIENT_SECRET, SERVOSITY_MSP_TOKEN).

Step 3 - Ask a real question

Honest status

The cli-printing-press frontmatter + README install sections ship today, and the MCP path (B) is the reliable route. End-to-end Skill install from a non-canonical monorepo subdirectory (Servosity/msp-skills/...) has not been fully verified upstream - if Path A doesn’t resolve, use Path B.

What’s next

← Back to main install