Hermes MCP Bridge
Provides read-only tools for interacting with a Hermes gateway, including checking agent status, mission control summary, listing channels, and pending approvals.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Hermes MCP Bridge
Read-only MCP bridge exposing Hermes gateway tools to ChatGPT via HTTP/SSE.
Endpoints
/mcp— StreamableHTTP (primary, MCP spec standard)/sse— Server-Sent Events (fallback for legacy clients)/health— Health check (no auth)
Read-Only Tools Exposed
Tool | Description |
| Current Hermes agent status |
| Mission Control dashboard summary |
| List messaging channels |
| List pending approval requests |
Blocked (never exposed):
messages_sendpermissions_respondAny write/execute/create/delete tools
Local Development
# Install deps
pip install -r requirements.txt
# Run (requires Hermes gateway at http://127.0.0.1:8642)
PORT=8080 uvicorn app:app --host 0.0.0.0 --port 8080
# Or with custom Hermes URL
HERMES_GATEWAY_URL=http://localhost:8640 PORT=8080 uvicorn app:app --host 0.0.0.0Environment Variables
Variable | Default | Description |
|
| Bind port (Zeabur injects this) |
|
| Hermes gateway base URL |
| (unset) | Optional Bearer token for auth |
Zeabur Deployment
Push this repo to Git
In Zeabur dashboard: Add Service → Git Repository
Select this repo
Important: Disable "Public" toggle (private service)
Zeabur auto-detects Python, runs
uvicorn app:app --host 0.0.0.0 --port $PORTService gets internal DNS:
http://hermes-mcp-bridge:8080
Phase 2 Network Note
On Zeabur, each service is a separate container. The bridge cannot reach Hermes at 127.0.0.1:8642.
Required for Phase 2: Expose Hermes gateway as an internal Zeabur Service (no public toggle) on port 8642, then set:
HERMES_GATEWAY_URL=http://hermes-gateway:8642in the bridge service environment.
Auth
If MCP_BRIDGE_TOKEN is set, all /mcp and /sse requests require:
Authorization: Bearer <MCP_BRIDGE_TOKEN>ChatGPT MCP config example:
{
"mcpServers": {
"hermes": {
"url": "https://hermes-mcp-bridge.zeabur.app/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}License
Internal tool — not for public distribution.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Read-only discovery of ChatGXT's integration catalog and public MCP capabilities.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.