Hermes
Add Xentropy to Hermes Agent in config.yaml and sign in with OAuth or an API key header.
Hermes Agent reads MCP servers from ~/.hermes/config.yaml.
Connect with OAuth
-
Add the server to
~/.hermes/config.yaml:mcp_servers: xentropy: url: https://api.xentropy.ai/mcp auth: oauth -
Sign in:
hermes mcp login xentropy -
Sign in to Xentropy in the browser and review the requested access. Hermes listens on a loopback port on your machine for the result.
Xentropy tools appear in Hermes as mcp_xentropy_<tool> in the
mcp-xentropy toolset.
Approve writes
Add trust: untrusted under xentropy so Hermes asks before each call that
writes.
Headless use with an API key
Create a key with the Agent preset under Settings → API Keys and put
it in ~/.hermes/.env as XENTROPY_API_KEY. Then send it as a header instead
of signing in:
mcp_servers:
xentropy:
url: https://api.xentropy.ai/mcp
headers:
Authorization: "Bearer ${XENTROPY_API_KEY}"Device-flow sign-in is not available for Xentropy yet. On headless or gateway hosts, use this API-key header variant.
Skills
Xentropy publishes its skills at https://xentropy.ai/.well-known/skills/.
Install one with:
hermes skills install well-known:https://xentropy.ai/.well-known/skills/xentropy-artifactsA listing in the Hermes plugin catalog is coming soon too. Until then, add Xentropy with the config above.
Scopes to grant
OAuth sign-in offers the agent default scopes: artifacts:read,
artifacts:write, artifacts:render, dashboards:read, dashboards:write,
data:read, data:write and connections:read. The Agent preset for API
keys matches that set. See API keys and scopes.
Troubleshooting
- New tools are missing. Hermes lists tools when it connects. After a Xentropy update, restart Hermes.
- Authentication needed again. Run
hermes mcp login xentropy. - Revoked or expired. OAuth connections appear in Agent access → Connected assistants; API keys under Settings → API Keys.