Official issues about MCP server connections and tool loading. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
On xai-oauth with grok-4.3, optional multiline string args are dropped from MCP tool calls, causing AgentMail to send blank emails while reporting success.
Integration proposal from the Gotong project: Hermes as the personal agent layer inside a governed workflow hub.
A non-interactive gateway run can stay stuck in MCP OAuth discovery for the full browser-callback timeout when token refresh fails, and retries then fail because the callback port is still in use. This issue is now closed.
Long-lived Hermes worker processes accumulate orphaned MCP stdio subprocesses over time (53 in the reported case), causing SQLite DB handle contention and intermittent memory tool failures even though health checks report the MCP server as healthy.
In oneshot mode (hermes -z), the agent's tool list is built before MCP discovery registers dynamic MCP tools/aliases, so tools from configured MCP servers are never available even though they pass hermes mcp test.
Starting the MCP server after a standard pip install crashes due to a module path issue. Labeled P2 by maintainers, so a workaround exists.
Reinstall as a full package, clear stale caches, and restart. After changing config, reset the session so the MCP reloads.
Feature request to support an HTTPS OAuth redirect_uri override for MCP, since some OAuth providers (e.g. Salesforce) reject the current localhost HTTP callback format.
Back to curated issues . School solution cards . Troubleshooting