Version Packages

[agentprism-releases]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@automatalabs/mcp-server@0.27.1

Patch Changes

• 217ba32: Fix a race that could leave a freshly connected client with no workflow tool.

  Registration was gated on notifications/initialized, but a notification carries no
  ordering guarantee against the requests that follow it — and over the stdio shim each
  frame becomes its own HTTP POST to the daemon. A client that pipelined initialized with
  its first tools/list or tools/call could reach a server with nothing registered,
  surfacing as an empty tool list or a tool-not-found result on the first call.

  The workflow tool is now registered at server construction, so it exists for the whole
  life of the session. Capability negotiation is unchanged for the MCP Apps surface: the
  panel resource, the app-only workflow-events tool, and the tool's UI metadata are still
  added only for a client that advertised io.modelcontextprotocol/ui, and the resulting
  tools/list_changed prompts a capable client to re-list.

  The shim now also forwards client frames in the order they were sent; previously each
  frame was dispatched without sequencing, so consecutive frames could race as concurrent
  POSTs and arrive out of order.

• Updated dependencies [217ba32]

  • @automatalabs/workflows@0.47.1
  • @automatalabs/repl-engine@0.1.8

@automatalabs/repl-engine@0.1.8

Patch Changes

• Updated dependencies [217ba32]
  • @automatalabs/workflows@0.47.1

@automatalabs/workflows@0.47.1

Patch Changes

• 217ba32: Fix a race that could leave a freshly connected client with no workflow tool.

  Registration was gated on notifications/initialized, but a notification carries no
  ordering guarantee against the requests that follow it — and over the stdio shim each
  frame becomes its own HTTP POST to the daemon. A client that pipelined initialized with
  its first tools/list or tools/call could reach a server with nothing registered,
  surfacing as an empty tool list or a tool-not-found result on the first call.

  The workflow tool is now registered at server construction, so it exists for the whole
  life of the session. Capability negotiation is unchanged for the MCP Apps surface: the
  panel resource, the app-only workflow-events tool, and the tool's UI metadata are still
  added only for a client that advertised io.modelcontextprotocol/ui, and the resulting
  tools/list_changed prompts a capable client to re-list.

  The shim now also forwards client frames in the order they were sent; previously each
  frame was dispatched without sequencing, so consecutive frames could race as concurrent
  POSTs and arrive out of order.

  • @automatalabs/repl-engine@0.1.8