@executor-js/sdk

1.5.29

1.5.28

Patch Changes

• #1246 1c48182 Thanks @RhysSullivan! - Keep MCP tool catalogs in sync with the server's live tool set. Previously a connection's tools were listed once at create time and never updated unless the integration's config changed or a user clicked Refresh, so server-side tool changes silently broke invocations.
  • tools/list discovery now follows nextCursor pagination per the MCP spec, so servers with paginated catalogs list completely instead of first-page-only.
  • The client handles notifications/tools/list_changed received during a tool call and marks the connection's persisted catalog stale; the next tools read re-lists from the server.
  • An unknown-tool rejection from the server (protocol error or the reference SDK's error envelope) returns a typed mcp_tool_unknown failure telling the caller to re-list, and marks the catalog stale so it heals on the next read.
  • Remote catalogs now also refresh on read once older than a freshness TTL (ExecutorConfig.toolsSyncTtlMs, default 15 minutes, null to disable), covering servers that change tools without notifying.
  • A failed listing (server unreachable, auth not ready) no longer wipes the previously persisted catalog; it is kept and retried after the TTL.

1.5.27

1.5.26

1.5.25

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

Patch Changes

• Surface binary tool results as model-native file outputs across OpenAPI and upstream MCP integrations.

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

Patch Changes

• #964 7cee242 Thanks @RhysSullivan! - Faster integrations with large API specs

  Resolved OpenAPI spec text and GraphQL introspection snapshots are now stored content-addressed in the plugin blob store instead of inline in each integration's stored config. Listing integrations no longer loads multi-megabyte spec blobs it immediately discards, which makes the integrations surface dramatically faster for workspaces with large specs. Existing integrations keep working: rows that still inline a spec resolve unchanged and are rewritten in place the next time they are imported or refreshed.

• #964 7cee242 Thanks @RhysSullivan! - Republish from committed source. Versions 1.5.5 and 1.5.6 of the library packages were published directly to npm to fix installs resolving the wrong fumadb dependency (the vendored database layer is now scoped as @executor-js/fumadb); that fix landed in the repo separately, and this release brings the recorded package versions back in line with npm.

• Updated dependencies [7cee242]:

  • @executor-js/fumadb@1.5.7

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

Patch Changes

• #893 7d7fbbd Thanks @dmmulroy! - Batch OpenAPI operation metadata writes through plugin storage so adding large built-in OpenAPI sources no longer performs thousands of sequential D1 operations.

• #922 1ba0193 Thanks @RhysSullivan! - Move effect from dependencies to peerDependencies in the published library packages so consumers provide a single shared Effect instance.