Executor as MCP server: serve spec 2026-07-28 and consolidate onto SDK v2 - #1611
Draft
RhysSullivan wants to merge 10 commits into
Draft
Executor as MCP server: serve spec 2026-07-28 and consolidate onto SDK v2#1611RhysSullivan wants to merge 10 commits into
RhysSullivan wants to merge 10 commits into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | aaace6b | Aug 16 2026, 04:02 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | aaace6b | Commit Preview URL Branch Preview URL |
Aug 16 2026, 04:02 PM |
Contributor
Cloudflare preview
Sign-in is Cloudflare Access (one-time PIN to an allowed email). The preview has its own database and encryption key; it is destroyed when this PR closes. |
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
This was referenced Aug 16, 2026
RhysSullivan
changed the base branch from
mcp-server-v2-cloud
to
mcp-client-v2
August 16, 2026 16:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Executor as an MCP server on spec 2026-07-28 (part 2 of 2, stacked on the client PR): every host serves modern clients, and all serving — both eras — consolidates onto SDK v2.
Serving the new spec:
McpServer, serving both eras. Native elicitation =input_required+ HMAC-signedrequestState(principal+method bound, TTL'd) over the existing pause/resume engine; legacy clients get realelicitation/createvia the SDK's shim. MCP Apps helpers vendored wire-identical pending upstream ext-apps v2 ([codex] Put typed base URL first in combobox #702).serveStdio. CORS preflights echo requested headers for dynamicMcp-Param-<name>.tools/callroutes into DOs for execution affinity via the executionId-keyed owner directory (continuations verify signed state in the worker; same cross-bearer 403 contract as legacy).Consolidation (deletes the transitional machinery):
McpAgentonto our own Durable Object hosting the v2 stack: DO-storageEventStore(trim/oversize/best-effort), cross-stream replay of stranded POST responses onto the next standalone GET, compatibility priming for pre-2025-11-25clients, SSE max-age rotation, transactional idle-dispose, parse guard so unknown/foreign session ids 404 cleanly.patches/[email protected](911 lines), theagentsdependency from every MCP path, the v1 tool-server assembly, theext-appsruntime dependency, all transitionalV2naming.@modelcontextprotocol/sdkv1 survives only as a devDependency for legacy-client interop tests and the deliberately-legacyplugins/mcptest fixture.Evidence: full CI green at this tip (19 checks incl. all cloud e2e shards). The four patch-behavior suites — priming reconnect, SSE replay, oversize response, transport-brick regression — plus session survival are the acceptance gate for the consolidation, all green. Modern serving proven live with a
2026-07-28-pinned client; legacy proven by real v1-SDK clients in tests.Deployment prerequisite (before merge): both workers need the shared continuation-signing secret (≥32 bytes):
wrangler secret put MCP_REQUEST_STATE_KEY. No generated fallback.One-time cutover: cloud sessions created before this deploy get a clean 404 and clients re-initialize transparently. Deploy in a quiet window and watch reconnects. (If a staged rollback is ever needed, the additive-serving/consolidation seam survives in the commit history at
mcp-server-v2-cloud.)