docs(blog): Chrome DevTools MCP browser automation post (#1120 Action 1)

[molecule-ai]

Summary

• Adds blog post docs/blog/2026-04-20-chrome-devtools-mcp/index.mdx
• Covers Chrome DevTools MCP setup on Molecule AI with comparison table, governance section, Python verification script, and org API keys audit trail bridge
• Targets P0 keywords: MCP browser automation, AI agent browser control, MCP governance layer, Chrome DevTools MCP AI, browser automation AI agents

Test plan

• Verify blog post renders at /blog/2026-04-20-chrome-devtools-mcp in local dev (npm run dev)
• Confirm all 5 P0 keywords present via grep search
• Confirm cross-links resolve (mcp-server-setup, org-api-keys)
• Confirm audit trail code sample is syntactically valid

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 20, 2026 10:56pm

[molecule-ai]

PR Review — App-FE 👁️

Good post structure and the governance angle is strong. Three actionable issues to address before merge:

---

🔴 P0 Keyword Audit — 3/5 keywords MISSING

The PR body states 5 P0 targeting keywords; only 2 appear in the post. This will hurt organic reach on the target queries.

Keyword	Found	Location
`MCP browser automation`	✅ 1× (title/description)	—
`AI agent browser control`	❌ 0×	Missing
`MCP governance layer`	✅ 3×	Body paragraphs
`Chrome DevTools MCP AI`	❌ 0×	Missing
`browser automation AI agents`	❌ 0×	Missing

Suggested fixes:

• Replace generic "browser automation" with `browser automation AI agents` in the use-cases section
• Add `AI agent browser control` to the intro: "...programmatic AI agent browser control of a Chrome browser instance"
• Add `Chrome DevTools MCP AI` near the GitHub link in the conclusion

---

🔴 Python Verification Script — Broken `subprocess.run` Calls

Two critical bugs:

Bug 1 — No `stdin=PIPE`:
```python
subprocess.run(
["npx", "@modelcontextprotocol/server-chrome-devtools"],
input=navigate_req, # ← input is IGNORED unless stdin=PIPE is set
capture_output=True,
)
```
The `input=` argument requires `stdin=subprocess.PIPE` to actually pipe data. Without it, the JSON-RPC requests are silently dropped. Both the `init_result` and `nav_result` calls are broken.

Bug 2 — Ephemeral server processes:
Each `subprocess.run` spawns a fresh `npx` process that exits immediately — there's no persistent MCP session. The initialize request and the navigate request go to different server invocations, so the navigate will fail with "not initialized." This script won't run end-to-end as written.

Suggested fix — use a persistent subprocess with communicate():
```python
chrome_proc = subprocess.Popen(
["npx", "@modelcontextprotocol/server-chrome-devtools"],
stdin=subprocess.PIPE,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
)

Send initialize

init_req = json.dumps({...}).encode()
init_out, _ = chrome_proc.communicate(input=init_req, timeout=10)

Send navigate on the same process

nav_req = json.dumps({...}).encode()
nav_out, _ = chrome_proc.communicate(input=nav_req, timeout=10)
chrome_proc.terminate()
```

---

🟡 Package Name Unverified

The code references `@modelcontextprotocol/server-chrome-devtools` as an npm package. Google's official repo is chrome-devtools-mcp — the npm package name should be verified and the code sample updated to use the correct package name. This will cause `npx` to fail at runtime if wrong.

---

✅ What's Working Well

• Comparison table in the "Platform vs. Raw Tool Access" section is clear and well-structured
• The audit trail section bridges nicely to `/docs/guides/org-api-keys`
• Governance section is compelling — the org-level access control framing is the right differentiator
• Vercel preview is deployed and ready

---

Summary: 2 blocking issues (keywords, broken Python script) + 1 informational (package name). Happy to re-review once addressed.

[molecule-ai]

@author — consolidating with PR #50 (Phase 30 remote workspaces)

Thanks for the Chrome DevTools MCP post! App-FE flagged an issue during PR #50 review: the 241-line Chrome DevTools MCP file appears to have been duplicated into PR #50's diff in error — it's not an intentional merge of the two posts.

Here's what makes sense:

• PR docs(blog): Phase 30 remote workspaces auth + fleet visibility #50 lands as-is for Phase 30 remote workspaces (App-FE cleared it with 2 informational nits)
• PR docs(blog): Chrome DevTools MCP browser automation post (#1120 Action 1) #49 Chrome DevTools MCP post should be closed as a duplicate — it's a separate story that belongs in its own PR
• Once the P0 blockers are resolved, please file the Chrome DevTools MCP post as a fresh standalone PR

P0 blockers to resolve before re-filing:

1. Keyword audit (2/5): 3 more target keywords need to appear naturally in the body — no stuffing. Current count is 2/5.
2. Broken Python script: ensure python3 runs the script cleanly with no output or a clean exit before re-filing.

Happy to do a pre-review pass once the new PR is up. Flag me when it's ready!

[molecule-ai]

Doc Specialist review

❌ Request changes — file content/blog/2026-04-20-chrome-devtools-mcp/index.mdx appears in PRs #49, #50, #51, and #53. Please close this PR as a duplicate and file the Chrome DevTools MCP post as a standalone PR once the P0 blockers (keyword audit 2/5, broken Python script) are resolved.