Subtext CLI — drive the Subtext MCP server from your terminal
Subtext CLI — drive the Subtext MCP server from your terminal. Exposed over MCP by the subtext mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A command-line interface for the Subtext MCP server. Open a browser, inspect the page, click things, take screenshots — from a shell or CI script.
The Subtext CLI opens a hosted browser session and lets you drive it: navigate, inspect the DOM, click, type, take screenshots, and close — all from a shell. Built for AI agents and CI pipelines, but works just as well for manual spot-checks.
Everything the assistant can do here goes through one of these:
Namespace — Typelive — passthroughcomment — passthroughdoc — passthroughartifact — passthroughprivacy — passthroughreview — passthroughtunnel — nativesightmap — nativeauth — nativeversion — nativeVerify — The Verify tool exposed by this serverYou will need 6 environment variables: SUBTEXT_API_KEY, SUBTEXT_REGION, RELAY_URL, SIGHTMAP_URL, TRACE_URL, TUNNEL_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Subtext's toolset — Namespace, live, comment and 10 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Namespace | Type |
| live | passthrough |
| comment | passthrough |
| doc | passthrough |
| artifact | passthrough |
| privacy | passthrough |
| review | passthrough |
| tunnel | native |
| sightmap | native |
| auth | native |
| version | native |
| Verify | The Verify tool exposed by this server. |
| Sightmaps | .sightmap/ YAML files in your project root map CSS selectors and routes to semantic component names. After uploading, the hosted browser resolves those names in snapshots, screenshots, and interaction targets. Upload the |
{
"mcpServers": {
"subtext": {
"command": "npx",
"args": ["-y", "@subtextdev/subtext-cli"],
"env": {
"SUBTEXT_API_KEY": "your-value",
"SUBTEXT_REGION": "your-value",
"RELAY_URL": "your-value",
"SIGHTMAP_URL": "your-value",
"TRACE_URL": "your-value",
"TUNNEL_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SUBTEXT_API_KEY | Credential the server authenticates with. | Yes |
| SUBTEXT_REGION | Configuration value read at startup. | Optional |
| RELAY_URL | Endpoint or connection string the server talks to. | Yes |
| SIGHTMAP_URL | Endpoint or connection string the server talks to. | Yes |
| TRACE_URL | Endpoint or connection string the server talks to. | Yes |
| TUNNEL_ID | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.