Hermes reads the standard SKILL.md and runs locally, so the skill installs the groniz CLI and it just works. Or add the MCP server and allowlist exactly the tools it may call.
Hermes installs a skill straight from a URL. It runs on your machine, so the skill installs the groniz CLI and calls it normally — no sandbox egress to configure.
hermes skills install https://groniz.com/SKILL.mdPrefer typed tools? Add Groniz to config.yaml with your key as a header, and list exactly the tools you want Hermes to have.
mcp_servers:
groniz:
url: "https://mcp.groniz.com/mcp"
headers:
Authorization: "Bearer YOUR_API_KEY"
tools:
include: [integrationList, schedulePostTool, integrationSchema]The Groniz surface is the same everywhere; what changes is how Hermes Agent reaches for it.
Try Give Hermes just the posting tools, and nothing else it could misuse.
Hermes lets you allowlist exactly which tools it may call, so the distinctive move is scoping it tight: list schedulePostTool and integrationList, leave the rest off.
Every command below runs against your real Groniz account — the same posting, scheduling and analytics the Console gives you.
integrationListlist your connected accountsgroupListlist customer groupsintegrationSchemaget a channel’s posting rulestriggerToolrun channel helpers (Discord channels, Reddit flairs…)schedulePostToolschedule, draft or publish a postgenerateImageToolgenerate an image for a postgenerateVideoOptionslist video-generation optionsvideoFunctionToolread video generator settingsgenerateVideoToolgenerate a video for a postgroniz integrations:listlist connected accountsgroniz integrations:settingsget an account’s settings schemagroniz integrations:triggerrun a channel helpergroniz posts:createcreate or schedule a postgroniz posts:listlist postsgroniz posts:deletedelete a postgroniz analytics:platformread channel analyticsgroniz analytics:postread a post’s analyticsgroniz uploadupload mediaGive your agent posting power, or open the Console — free to try, cancel anytime.