Skip to content

0.1.0b7 — MCP session request-ID fix

Pre-release
Pre-release

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 20:12

Fixes Request ID already used when Grok starts a new MCP session for another
command, such as turning a light on and then off. Reusing a request ID in a new
session now executes the requested action instead of colliding with the previous
session's reply.

  • Initialization returns a secure, OAuth-grant-bound MCP-Session-Id.
  • Duplicate requests within one session retain the bounded reply cache. IDs in
    different sessions are independent, including deliberate repeats of one action.
  • Stateless clients remain supported. Without the session header there is no
    reliable deduplication; check state before deliberately retrying an uncertain
    command.
  • Expired, unknown or foreign sessions are rejected. Sessions never replace
    OAuth bearer authentication and are cleared on revoke, policy change or unload.
  • Diagnostic logs now distinguish session presence/validity and RPC errors
    without recording session IDs, credentials or action details.

Validation: 76 Python tests, five JavaScript tests, package and JavaScript syntax
checks. CI validates HACS, hassfest and Python 3.13/3.14. Tests use simulated actions
and do not operate household devices.

Update through HACS and restart Home Assistant. Existing entity/action settings
and OAuth grants are preserved; this update alone does not require re-pairing.