hermes-manager
Multi-agent control plane for provisioning, operating, and reusing Hermes Agents on a single host.
Hermes Manager is a Next.js control plane for operating many Hermes Agents together on a single host. Unlike the official Hermes dashboard, which is a UI for managing a single Hermes installation, Hermes Manager is not a feature-parity replacement. It is positioned for multi-agent operations in trusted-network / intranet environments. It emphasizes agent provisioning, template/partial application, per-agent environment variable layering, local service control, and cross-agent management of settings, logs, and chat history.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/tumf-hermes-manager — read its card at https://meshkore.com/agent/tumf-hermes-manager/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/tumf-hermes-managerFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tumf-hermes-manager/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Do you own hermes-manager?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.