hermes-mcp-bridge
by Heldinhow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for the bridge to listen on. Default: 8765. | 8765 |
| TASKS_DIR | Yes | Directory holding one subdirectory per task id, created on demand; files are only reachable through hermes_result and hermes_files. Use absolute or $HOME paths (~ is not expanded). | |
| AGENTS_FILE | No | Path to the YAML registry file for agents. Default: ~/.hermes/agents.yaml. | ~/.hermes/agents.yaml |
| MCP_AUTH_TOKEN | Yes | A single 64-hex-character bearer token generated from 32 random bytes, stored only in .env (mode 600), never taken from argv or written to logs. | |
| HERMES_ENV_PATH | Yes | Path to the file holding the local agent's API_SERVER_KEY. Optional API_SERVER_HOST and API_SERVER_PORT values are read from it (defaults: 127.0.0.1:8642). | |
| HERMES_CONTRACT_PATH | No | Path to a Markdown contract injected as system instructions on every hermes_task. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues