Skip to content

v1.1.0 — Stateless MCP with legacy compatibility

Choose a tag to compare

@i1rr i1rr released this 17 Nov 11:01

Adds MCP 2026-07-28 stateless HTTP while retaining the existing 2025-03-26 and 2025-11-25 clients and public callback/session APIs.

  • Per-request discovery, version/capability metadata, routing-header validation and modern result envelopes.
  • Bounded request-scoped SSE, disconnect/timeout cancellation and one-time deferred cleanup. Subscription acknowledgment grants no optional change feed; streams are not resumable.
  • Separate modern Dashboard activity and owner cancellation from legacy sessions. Client labels never grant authority.
  • Preserve explicit application handles and reject refresh-ID reuse with different import options. Unknown mutation outcomes still require inspection.

Validated on Windows with Unity 6000.6.9f1: the exact signed archive passes 531 Editor tests, 41 graphical runtime tests and 7 native socket tests. Unity reports its signature Valid. A clean package-only install works. A Mono development player passes modern SDK discovery, reads, deferred SSE, subscriptions, cancellation and required authentication, plus both legacy versions. The normal player contains neither the MCP runtime assembly nor its token.

Direct Codex MCP client 0.169.0-alpha.11.1 passes discovery, read, mutation/readback, deferred work and reconnect using legacy 2025-03-26. Official TypeScript client SDK 2.4.0 separately passes those workflows over 2026-07-28 without initialize or session headers. Updating the server does not upgrade a client's selected protocol. Independent Claude Code/Cursor and non-Windows acceptance remain unverified. Cloud CI was not run; these are local results, with no IL2CPP or broad performance/conformance claim.

Known update limitation: #14 tracks stale native keepers when a live Windows UPM change moves the plugin path. Close the Editor before changing the installed package source/cache path, reopen it and reobserve the endpoint. A restart is a workaround, not a hot-update fix. Same-path managed reload behavior is separately verified.

Install through the signed Unity registry at https://i1rr.github.io/unity-MCP, scoped only to i1rr-unity-mcp, or use the immutable Git URL:

https://github.com/i1rr/unity-MCP.git#v1.1.0

Commit: d797e561f24c6771a65e4df3da69989c0dfd41bf

Signed archive SHA-256: f35fcf346c5d107fb6d3c1be667803dbbc0d147b749998df3909723c1eef5450

The package still declares Unity 2022.3 as its minimum; that declaration is not a fresh test result for that Editor version.