smooth-operator-mcp 3.0.4 → 3.0.6

package/.env.example

@@ -30,6 +30,9 @@ SMOOTH_OPERATOR_BROWSER_CONNECT_TIMEOUT_MS=30000
 SMOOTH_OPERATOR_BROWSER_CDP_TIMEOUT_MS=30000
 SMOOTH_OPERATOR_MAX_SCREENSHOT_BYTES=8000000
 SMOOTH_OPERATOR_MAX_HTML_CHARS=200000
+# Optional idle cleanup for the connected browser; 0 disables idle cleanup.
+# The maximum accepted value is 86400000 ms (24 hours).
+# SMOOTH_OPERATOR_BROWSER_IDLE_TIMEOUT_MS=0
 
 # Network and page-operation safety invariants
 SMOOTH_OPERATOR_ALLOWED_DOMAINS=

package/README.md

@@ -39,6 +39,15 @@ Verify: `smooth-operator --help` and `server_health` / `browser_doctor` appear a
 - Inspect pages with snapshots, accessibility trees, HTML, styles, text search, and bounded extraction
 - Work across tabs, frames, popups, shadow DOM, dialogs, cookies, storage, downloads, screenshots, and PDFs
 - Search the web through bounded DuckDuckGo retrieval
+- Search a bounded metadata-only network journal by request ID, URL, method, status, and resource type
+- Block page-scoped image, stylesheet, font, media, and script subresources; document and navigation requests are never selectable
+- Inspect a selected element's safe attributes, styles, animations, and shallow children without returning scripts, event source, form values, or arbitrary data attributes
+- Upload one file or up to 20 files from allowed roots; each file is capped at 50 MiB and the aggregate at 100 MiB
+- Read, set, and delete URL-scoped cookies with validated SameSite settings; cookie values are omitted from reads
+
+The MCP registry exposes 64 public tools. The surface includes bounded network
+search, safe element inspection, page-scoped resource blocking, and file and
+cookie controls alongside the navigation, extraction, and lifecycle tools.
 
 Ask: *“Scrape pricing into a table”*, *“Fill this form with ~/resume.pdf”*, or *“Download the monthly report as a PDF.”*
 
@@ -57,6 +66,13 @@ cancellable. All local browser tools and page features are available by default;
 remote HTTP, private-network access, and file roots remain explicitly gated.
 Faster calls do not bypass challenges or grant permission to automate a site.
 
+Managed mode preflights a regular executable when it needs to launch, and
+launch mode does so before invoking Chromium. Both wait for browser launch
+readiness and a target-guard acknowledgement before returning a usable
+connection. The loopback DevTools `/json/version` probe is bounded to 64 KiB
+before JSON parsing. There is no arbitrary CDP or host-code tool; page
+evaluation remains an explicit page capability.
+
 ## Why
 
 - Zero setup — managed, headed, persistent browser by default