
Hermes Agent Mcp
io.github.woonyong-choiPublished by GitHub account woonyong-choiv0.1.1Updated Oct 24, 2026
Operate a local Hermes Agent install over stdio: tasks, cron, config, gateway, doctor. No network.
Overview
Lets an MCP client operate a local Hermes Agent install over stdio: tasks, cron jobs, config, gateway, doctor and skills.
- What you can do
- Wraps the local hermes CLI over stdio and exposes around sixteen tools: hermes_ask for a one-shot task, cron list/create/edit/run/runs, typed config_get and config_set against config.yaml, gateway status and restart, doctor, skills_list, sessions_list, model_info, and optional bridge tools that post prompts and replies into a chat. A shell tool exists but is disabled by default. Everything runs as a child process of the MCP client on the same machine, with no network listener.
- When to use it
- Use it when an MCP-capable assistant on the same machine needs to operate Hermes without a terminal: scheduling or editing cron jobs, changing configuration, restarting the gateway, or running health checks. It is a local alternative to remote Hermes bridges that expose the gateway over HTTP.
- Requirements
- Python with uv/uvx to run the PyPI package hermes-agent-mcp as a local stdio process. A local Hermes Agent install and its CLI on PATH, or set HERMES_MCP_BIN. Optional environment variables: HERMES_HOME, HERMES_MCP_ALLOW_WRITE, HERMES_MCP_ALLOW_SHELL, HERMES_MCP_TIMEOUT, HERMES_MCP_ASK_TIMEOUT, HERMES_MCP_MAX_OUTPUT, HERMES_MCP_CALLER, HERMES_MCP_LABEL_FORMAT. No network, ports, OAuth or credentials of its own.
Installation
In SourceWeft
- Open Hermes Agent Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 22, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.