hermes-mcp-gateway
Allows remote MCP clients to run governed one-shot tasks through Hermes Agent, including configurable profiles, toolsets, models, working directories, timeouts, approvals, and audit logging.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hermes-mcp-gatewaySearch my working directory for TODO comments using the file toolset."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hermes-mcp-gateway
A governed MCP gateway that exposes Hermes Agent one-shot task execution to remote MCP clients. This phase provides the foundations: validated YAML config, client secrets + short-lived JWTs, an RBAC policy engine, a SQLite audit store, a governed subprocess task executor, and a task-level human-in-the-loop approval queue.
The operator CLI and the MCP transport arrive in later phases; the entry point
hermes-mcp-gatewayis currently a stub that exits non-zero.
Layout
src/hermes_mcp_gateway/
config.py YAML config -> typed dataclasses (validation on load)
auth.py client secret verification + HS256 JWT issue/validate
policy.py toolset/model/workdir allowlists, approval gating
db.py SQLite (WAL) audit store: tasks, approvals, token issues
executor.py thread-per-task Hermes subprocess runner (capture/timeout/cancel)
approvals.py HITL queue helpers over the db functions
cli.py placeholder entry pointRelated MCP server: Astatide Conductor
Install
uv sync
uv run pytest -qConfiguration
Config is loaded from HERMES_MCP_GATEWAY_CONFIG or
~/.hermes/mcp-gateway/config.yaml. The template embeds no secrets: the JWT
signing key is read from the environment variable named by
auth.signing_secret_env.
server:
bind: 127.0.0.1
port: 8778
hermes:
bin: hermes
profile: mcp-worker
task_dir: /home/example/.hermes/mcp-gateway/tasks
db_path: /home/example/.hermes/mcp-gateway/gateway.db
timeout_s: 1800
auth:
issuer: hermes-mcp-gateway
signing_secret_env: HERMES_MCP_GATEWAY_SIGNING_KEY
token_ttl_s: 600
clients:
- client_id: example-client
secret_hash: sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
scopes:
- task:run
- toolset:file
- toolset:search
requires_approval: false
max_concurrency: 1
max_duration_s: 300
max_turns: 60
workdirs:
- /home/example/src
models:
- deepseek-v4-flashSet the signing key (at least 32 characters) before starting:
export HERMES_MCP_GATEWAY_SIGNING_KEY="<a long random value, e.g. 40+ chars>"Execution contract
TaskExecutor.run() spawns:
hermes -p <profile> chat -q "<prompt>" [-t <toolsets>] [-m <model>] \
--source mcp:<client_id> --max-turns <max_turns> -Qwith cwd=<workdir>, stdout/stderr captured to
<task_dir>/<task_id>/stdout.txt and stderr.txt, and a status.json written
atomically on every transition. The Hermes session id is parsed out of stderr.
--yolo is never passed; approval timeouts and non-TTY dangerous-command
denials stay at Hermes defaults.
Tasks survive gateway restarts: status.json and the DB are the source of
truth, and tasks left running for over an hour are reconciled to failed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceOrchestrates persistent task graphs and enforces approval policies for MCP-driven agent workflows, coordinating with Agents Gateway for execution.MIT
- AlicenseBqualityCmaintenanceA safety-first MCP operations cockpit for Hermes Agent installations, exposing typed, evidence-producing management primitives.73MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible LLM clients to execute server-verified agent workflows, with enforced transitions, invocation caps, and signed audit trails.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rmax-ai/hermes-mcp-gateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server