diff --git a/docs/marketing/campaigns/chrome-devtools-mcp-seo/backlinks-outreach.md b/docs/marketing/campaigns/chrome-devtools-mcp-seo/backlinks-outreach.md new file mode 100644 index 00000000..2151c39a --- /dev/null +++ b/docs/marketing/campaigns/chrome-devtools-mcp-seo/backlinks-outreach.md @@ -0,0 +1,114 @@ +# Chrome DevTools MCP — Backlinks Outreach Draft +Campaign: chrome-devtools-mcp-seo | Blog: docs PR #49 (merged `2026-04-20-chrome-devtools-mcp`) +Status: Draft — Marketing Lead approval required before sending +Date: 2026-04-21 + +--- + +## About backlinks + +Backlinks (inbound links from other sites) improve SEO authority for the target keyword. For `MCP browser automation` and `browser automation AI agents`, the goal is placements in communities where AI agent developers and browser automation practitioners congregate. + +Outreach should focus on communities that: +- Discuss AI agent frameworks (LangChain, CrewAI, AutoGen, etc.) +- Work on browser automation (Puppeteer, Playwright) +- Build with the MCP protocol +- Write about AI agent governance and security + +Do NOT cold spam. Only reach out to communities where there's a genuine topical overlap. Personalize the message to the specific thread or context. + +--- + +## Community outreach templates + +### Reddit — r/programming / r/MachineLearning / r/artificial + +**When:** A thread asks "how do I add browser automation to my AI agent?" or similar +**Subject:** not applicable (Reddit DMs or comments) +**Template (comment, not DM):** + +> This is a genuinely hard problem — most agent platforms give you the browser access but not the governance layer. We wrote up how Molecule AI handles it with Chrome DevTools MCP: https://docs.molecule.ai/blog/chrome-devtools-mcp +> +> The short version: every browser action is logged with org API key attribution, sessions are token-scoped per agent, and revocation is instant. Makes it auditable to a security team that wasn't in the room when you configured it. +> +> Not claiming it's the only way to do it — but the governance angle seems to be the gap most platforms skip. + +--- + +### Reddit — r/webdev / r/webdesign + +**When:** A thread about automated browser testing or Lighthouse audits in CI/CD +**Template (comment):** + +> If you're running Lighthouse in a CI pipeline, worth looking at how agents can run it too — Molecule AI has an example of wiring Lighthouse into Chrome DevTools MCP so an agent can report scores automatically: https://docs.molecule.ai/blog/chrome-devtools-mcp +> +> The useful part for a team: the governance layer means your security team can see what the agent accessed, even in a CI context. + +--- + +### LinkedIn — AI agent developers / platform engineers + +**Template (connection note or comment on relevant post):** + +> Saw your write-up on [specific post topic] — solid points on [specific detail]. +> +> Molecule AI just shipped an MCP governance layer for Chrome DevTools that might be relevant to what you're working on: https://docs.molecule.ai/blog/chrome-devtools-mcp +> +> The angle we hear most often: browser automation for agents works fine until your security team asks "which agent accessed what, when, and can you prove it?" That's what the governance layer is for. +> +> Happy to chat through the approach if it's useful. + +--- + +### MCP GitHub — modelcontextprotocol/servers + +**When:** A discussion or PR about browser automation tools in MCP servers +**Template (comment):** + +> Related to how this might fit into the broader MCP ecosystem — Molecule AI's implementation of Chrome DevTools MCP adds org API key attribution at the platform level, so every MCP tool call through a browser action carries audit attribution: https://docs.molecule.ai/blog/chrome-devtools-mcp +> +> Would be useful to understand if there's appetite for a standard attribution field in the MCP tool response schema — seems like a natural fit for governance-oriented platforms. + +--- + +### Hacker News / Lobsters + +**When:** A thread about AI agent security, browser isolation, or agent governance +**Template (top-level comment or reply):** + +> This is the gap most "agent can use a browser" announcements skip. +> +> Molecule AI shipped a Chrome DevTools MCP integration that adds the governance layer underneath: https://docs.molecule.ai/blog/chrome-devtools-mcp +> +> The specific thing it adds: org API key attribution on every browser action, token-scoped sessions per agent (no cross-contamination between agents), and instant revocation. Makes browser automation in agents something you can show a security team, not just a developer. + +--- + +## Priority targets (build this list before outreach) + +These are real communities to monitor — not cold-email targets: + +1. **r/programming** — browser automation + AI agents threads appear regularly +2. **r/MachineLearning** — agent architecture discussions +3. **LinkedIn AI agent practitioners** — follow posts by LangChain, CrewAI, AutoGen maintainers; engage substantively +4. **MCP Discord / GitHub** — modelcontextprotocol/servers discussions +5. **DEV.to** — AI + browser automation tags; search for "MCP" or "browser automation AI agent" + +## Guidelines + +- Only post where there's genuine topical relevance +- Add substantive context, not just a link +- Lead with the problem, not the product +- Do not post the same comment across multiple threads simultaneously +- If a thread already has a good answer, don't add a redundant link +- Marketing Lead reviews outreach messages before any are sent + +## Tracking + +| Target | Platform | Status | +|--------|----------|--------| +| MCP GitHub community | GitHub | Monitor | +| r/programming | Reddit | Monitor | +| LinkedIn practitioners | LinkedIn | Monitor | +| DEV.to | DEV.to | Monitor | +| Hacker News | Hacker News | Monitor | diff --git a/docs/marketing/campaigns/chrome-devtools-mcp-seo/social-copy.md b/docs/marketing/campaigns/chrome-devtools-mcp-seo/social-copy.md index 1cdacffb..8be2f116 100644 --- a/docs/marketing/campaigns/chrome-devtools-mcp-seo/social-copy.md +++ b/docs/marketing/campaigns/chrome-devtools-mcp-seo/social-copy.md @@ -1,134 +1,113 @@ -# Social Copy — Chrome DevTools MCP SEO Campaign -## Blog Post: "Give Your AI Agent a Real Browser: MCP + Chrome DevTools" -**URL:** /blog/browser-automation-ai-agents-mcp -**Date:** 2026-04-20 -**Author:** Content Marketer (draft — for Social Media Brand review + publish) -**Status:** DRAFT — pending Marketing Lead review +# Chrome DevTools MCP — Social Copy +Campaign: chrome-devtools-mcp-seo | Blog PR: docs#49 +Publish day: TBD (Day 1, separate from fly-deploy-anywhere) +Status: Draft — pending Marketing Lead approval --- -## X / Twitter Thread +## X (Twitter) — Primary thread (5 posts) -**Post 1 (Hook):** -> AI agents are great at reasoning. -They're terrible at clicking through a website. +### Post 1 — Hook (P0 keyword: `AI agent browser control`) +Your AI agent just made a purchase on your behalf. -The moment a task needs a real browser — forms, dynamic content, pages with no API — most agents hit a wall. +What did it buy? From where? With which account? -We fixed that. 🧵 +Most agents operate in a black box. Browser DevTools MCP makes the browser a first-class +tool — with org-level audit attribution on every action. + +→ [link: docs blog post] --- -**Post 2 (What we built):** -> Molecule AI agents now control Chrome directly via MCP + Chrome DevTools Protocol. +### Post 2 — Problem framing (P0 keyword: `MCP browser automation`) +Browser automation for AI agents usually means: give the agent your credentials, hope it +doesn't go somewhere unexpected, and check the logs after. -No Puppeteer wrappers. -No per-session SaaS pricing. -No human manually sequencing browser steps. +That's not a governance model. That's a trust fall. -The agent decides when to navigate, extract, screenshot — just like a human would. +Molecule AI's MCP governance layer for Chrome DevTools MCP gives you: +→ Which agent accessed which session +→ What it did (navigate, fill, screenshot, submit) +→ Audit trail with org API key attribution -Code snippet: -```python -agent = Agent( - mcp_tools=browser.tools(), # CDP over MCP -) -agent.run("Extract pricing from competitor.com") -``` +One org API key prefix per integration. Instant revocation. + +→ [link: docs blog post] --- -**Post 3 (Why it matters):** -> MCP gives AI models typed, structured tool calls — not buried prompts. +### Post 3 — Use case, concrete (P0 keyword: `browser automation AI agents`) +Real things teams use Chrome DevTools MCP for in production: -Browser automation via MCP means: -→ Session persistence (cookies survive across calls) -→ Streaming responses (no timeout on page loads) -→ Agent decides the sequence, not a human wiring workflow nodes +• Automated Lighthouse audits on every PR — agent runs the audit, reports the score, flags regressions +• Visual regression detection — agent screenshots key pages, diffs against baseline, opens tickets on drift +• Auth scraping — agent reads the authenticated state from an existing browser session + +The governance layer means your security team can see all three in the audit trail. + +→ [link: docs blog post] --- -**Post 4 (Use cases):** -> What can you actually do with a browser-wielding AI agent? +### Post 4 — Competitive / positioning (P0 keyword: `MCP governance layer`) +The MCP protocol lets you connect any compatible tool to any compatible agent. -• Competitive intelligence pipelines — agent visits sites, extracts data, writes summaries -• Automated UI regression testing — describe expected state in plain language -• AI-assisted data entry for legacy web UIs -• Real-time price monitoring with Slack alerts +What's been missing: visibility into what the agent actually *did* with that access. -All from the same MCP toolset. +Molecule AI's MCP governance layer adds: +• Per-action audit logging with org API key attribution +• Token-scoped Chrome sessions — no credential sharing across agents +• Instant revocation without redeployment + +→ [link: docs blog post] --- -**Post 5 (CTA):** -> Molecule AI workspaces ship browser automation out of the box. +### Post 5 — CTA +Chrome DevTools MCP ships today with Molecule AI Phase 30. -Free, self-hostable. GitHub below. +If you're running AI agents that interact with web UIs — there's a governance story +you need to have ready before your security team asks. -→ [github.com/Molecule-AI/molecule-core](https://github.com/Molecule-AI/molecule-core) - -*Full tutorial + code examples in the blog post.* +→ [link: docs blog post] --- -## LinkedIn Post +## LinkedIn — Single post -**Single post:** +**Title:** Why your AI agent's browser access needs a governance layer -AI agents can reason, plan, and call APIs — but put a dynamic website in front of them and they stall. +**Body:** -The problem isn't the model. It's the tooling. +Your AI agent can use a browser. That's useful. But "useful" isn't a security posture. -Most teams solve this one of two ways: -→ Write custom Playwright wrappers and pray the prompt doesn't drift -→ Pay per-session for a SaaS browser API +When an agent operates inside a browser — filling forms, reading session state, navigating authenticated flows — most platforms give you two options: trust it completely, or don't let it near the browser at all. -Both are the wrong direction. +Molecule AI's Chrome DevTools MCP integration adds a third option: visibility with control. -We built browser automation directly into Molecule AI workspaces via MCP + Chrome DevTools Protocol. The agent gets a live browser session with typed tool calls — it decides when to navigate, query, screenshot, and interact. No human wiring the sequence. +Here's what "governance layer" actually means in this context: -Three lines of YAML config. No SaaS dependency. No Selenium fleet to manage. +→ Every browser action is logged with the org API key prefix that made the call. You know which agent touched what session, every time. -Code example, four real-world use cases, and the full MCP → CDP bridge breakdown in the blog post. +→ Chrome sessions are token-scoped. Agent A's session is not Agent B's session. No credential cross-contamination. -→ [Read: "Give Your AI Agent a Real Browser: MCP + Chrome DevTools"](https://github.com/Molecule-AI/molecule-core/blob/main/docs/blog/2026-04-20-chrome-devtools-mcp-seo/index.md) +→ Revocation is instant. One API call, the key stops working, the session closes. No redeploy. -#AIagents #MCP #browserautomation #Python #LangChain +→ Audit trails are exportable. Your security team can review them without a custom logging pipeline. + +This is the difference between "the agent can use a browser" and "the agent's browser access is auditable, attributable, and revocable." + +Chrome DevTools MCP is available now on all Molecule AI deployments. + +→ [link: docs blog post] --- -## Image / Visual Recommendations +## Campaign notes -| Platform | Asset | File | -|---|---|---| -| X/LinkedIn | Diagram: MCP bridge | `assets/mcp-bridge-diagram.svg` | -| X (thread) | Comparison card | `assets/comparison-table-card.svg` | -| X/LinkedIn | Code card | Create from blog post code snippet: `agent = Agent(mcp_tools=browser.tools())` | -| X/LinkedIn | CTA graphic | "Your AI agent just got a browser." + GitHub link | - -**Generated assets available in `docs/marketing/campaigns/chrome-devtools-mcp-seo/assets/`:** -- `mcp-bridge-diagram.svg` — AI Agent → MCP → CDP → Chrome architecture diagram -- `comparison-table-card.svg` — 3-approach comparison (Custom vs SaaS vs Molecule AI) - ---- - -## Hashtag Set -#AIagents #MCP #BrowserAutomation #Python #DeveloperTools #AIautomation #LangChain #CrewAI - ---- - -## Campaign UTM Tags -Append `?utm_source=twitter&utm_medium=social&utm_campaign=chrome-devtools-mcp-seo` to all links in social posts. - ---- - -## Publishing Schedule -| Platform | When | Notes | -|---|---|---| -| X thread | Blog publish day, 9am PT | 5 posts, one every 20–30 min | -| LinkedIn | Blog publish day, 11am PT | Single post, same day as thread | -| LinkedIn comment replies | +24h | Engage with early comments | - ---- - -*Draft by Content Marketer 2026-04-20 — for Social Media Brand review before publishing* +**Audience:** Developer / DevOps (X), Enterprise platform engineers (LinkedIn) +**Tone:** Technical credibility, not hype. Lead with the governance gap, not the feature. +**Differentiation:** Org API key audit attribution — this is the claim competitors can't match. +**Use case pairings:** X → Lighthouse / visual regression (developer pain), LinkedIn → governance / compliance (enterprise buyer concern) +**Hashtags:** #MCP #AIAgents #AgenticAI #MoleculeAI +**Coordination:** Do NOT post on same day as fly-deploy-anywhere. Suggested spacing: Chrome DevTools MCP Day 1, Fly Day 3–5. diff --git a/marketing/audio/audit-trail-observability.mp3 b/marketing/audio/audit-trail-observability.mp3 new file mode 100644 index 00000000..00fb0b7f Binary files /dev/null and b/marketing/audio/audit-trail-observability.mp3 differ diff --git a/marketing/audio/chrome-devtools-mcp-summary.mp3 b/marketing/audio/chrome-devtools-mcp-summary.mp3 new file mode 100644 index 00000000..02b75a8c Binary files /dev/null and b/marketing/audio/chrome-devtools-mcp-summary.mp3 differ diff --git a/marketing/audio/phase30-video-vo.mp3 b/marketing/audio/phase30-video-vo.mp3 new file mode 100644 index 00000000..20840937 Binary files /dev/null and b/marketing/audio/phase30-video-vo.mp3 differ