Repository navigation
feat(gateway): read the website browser's card on its MCP port, like every MCP server's (FD-4701) - #558
Merged
earakely-scale merged 2 commits intoNov 9, 2026
Conversation
…every MCP server's (FD-4701) The VM deploy proxied the website browser's REST, its env card and computer-recording calls, to the Playwright MCP recorder's own port 18766, whatever browser filled the slot. Since 0.9.1475 the recorder fronts the MCP port and serves the card there, and both stages serve that image, so the gateway now reads every MCP server's card on its MCP port, as the containers deploy already does. `MCPServerConfig.card_port` goes. The image keeps serving its card on 18766 too, for installs from 0.9.1370 that still read it there; deploys made before this keep their compose file, 18766 included, across a snapshot reload. Tests: the compose and deploy units read the browser on its MCP port, a reload keeps an older deploy's 18766, the website e2e checks the deployed compose, and a new e2e kills the recorder and restarts the browser's container, then reads the card and records through the gateway after each. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…restart e2e The local sandbox rewrites /app in a script to the sandbox's own folder, so a lookup for /app/recorder.py matched nothing there; the recorder is the one process the image runs with /opt/recorder/bin/python. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
@greptileai review |
earakely-scale
deleted the
edgararakelyan/fd-4701-deploy-reads-browser-card-on-mcp-port
branch
November 9, 2026 16:27
Collaborator
Author
|
Real-provider e2e: 12/12 on Modal VM against dev. It deployed dev's
It was torn down afterwards. |
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.
What
The VM deploy now proxies the website browser's REST, meaning its env card and its
computer-recording/v1calls, to its MCP port, as it does for every other MCP server. The containers deploy already did this. Before, it sent them to the Playwright MCP recorder's own port 18766, whatever browser filled the slot.MCPServerConfig.card_portis removed. It existed only for this.This is FD-4701's PR 2. PR 1 (#548, v0.9.1475) made the recorder front the MCP port and serve the card there. Dev and prod both serve that image since Nov 9 (
playwright-mcpv3,sha256:5860038869cc). A browser that serves its card on its MCP port, such as chromium alone for M8.13, now fits the slot with no special case.Rollout
playwright_mcp/changes, so its source digest, tag and promotions stay as they are. The image keeps serving its card on 18766 as well, for installs from v0.9.1370 that still read it there. Dropping 18766 from the image is FD-5379, for later.depends_oneach MCP server being healthy, a TCP connect to its MCP port, so the browser's REST is up whenever the gateway is, at deploy and at reload. A killed recorder takes the front and 18766 down together, as before.playwright-mcpv2 has no card on its MCP port, so a rollback to v2 would drop the browser from the deploy's card (its tools still work). Prod's previous is v2 today, and it stops being the rollback target once a newer image is promoted.Tests
MCPServerConfig. A reload keeps an older deploy's:18766.test_gateway_with_single_website_envnow also checks the deployed compose'sREST_PROXY_URLS.test_the_browsers_card_and_recording_through_the_gateway_survive_its_recorder_and_container_restartingcovers the chaos case. It kills the recorder (the MCP server behind it keeps its pid) and then restarts the browser's container. After each, the card answers through the gateway and a recording through the gateway films the page.playwright_mcp_local_test.py),test_gateway_with_single_website_env, the new restart chaos test,test_gateway_with_multi_env_including_website,test_gateway_with_website_env_v1andtest_gateway_website_trigger_fires_on_a_request_through_the_website_proxy. The gateway tests' fixture images build for amd64 only.httpxin the system Python for the generated CLIs, no.gitin the synced tree, nounzip.children_environments == []). That is the breakage FD-5379 has to wait out.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge with the stated v3 browser-image rollback floor.Summary
New VM deployments read the website browser’s card and recording routes on its MCP port, like other MCP servers.
earakely-scale explicitly acknowledged that rolling the browser image back to v2 would remove its card from new deployments; v3 is the stated rollback floor.
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart LR C[Client] --> G[Gateway] G -->|Card and recording on MCP port| R[Browser recorder] G -->|MCP requests on same port| R R -->|Other requests| P[Playwright MCP]Reviews (1) · Last reviewed commit: "test(gateway): find the browser's record..." · Reviewed by Greptile