Every time the MCP container restarts (docker compose up -d), Hermes MCP client sessions are invalidated. The next tool call returns McpError: Session terminated and the agent must re-initialize (which sometimes requires 2-3 retries before succeeding).
Impact
During debugging (July 16 session), the container was restarted ~6 times for network/key fixes. Each restart required session renegotiation, adding friction to an already fragile flow.
Proposed Fix
Support stateless MCP requests where feasible (e.g., for idempotent read-only tools like list_folders)
Add a health-check endpoint the agent can ping before tool calls to detect stale sessions early
Investigate client-side auto-reconnect on 404/session-terminated responses
Context
This is primarily an MCP protocol / client issue, but the server should be robust against it.
## Problem
Every time the MCP container restarts (`docker compose up -d`), Hermes MCP client sessions are invalidated. The next tool call returns `McpError: Session terminated` and the agent must re-initialize (which sometimes requires 2-3 retries before succeeding).
## Impact
During debugging (July 16 session), the container was restarted ~6 times for network/key fixes. Each restart required session renegotiation, adding friction to an already fragile flow.
## Proposed Fix
- Support stateless MCP requests where feasible (e.g., for idempotent read-only tools like `list_folders`)
- Add a health-check endpoint the agent can ping before tool calls to detect stale sessions early
- Investigate client-side auto-reconnect on 404/session-terminated responses
## Context
This is primarily an MCP protocol / client issue, but the server should be robust against it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Every time the MCP container restarts (
docker compose up -d), Hermes MCP client sessions are invalidated. The next tool call returnsMcpError: Session terminatedand the agent must re-initialize (which sometimes requires 2-3 retries before succeeding).Impact
During debugging (July 16 session), the container was restarted ~6 times for network/key fixes. Each restart required session renegotiation, adding friction to an already fragile flow.
Proposed Fix
list_folders)Context
This is primarily an MCP protocol / client issue, but the server should be robust against it.