Skip to main content

Command Palette

Search for a command to run...

MCP & Mariner APIs: Agent Automation for Developers

Updated
3 min read
MCP & Mariner APIs: Agent Automation for Developers
D
PhD in Computational Linguistics. I build the operating systems for responsible AI. Founder of First AI Movers, helping companies move from "experimentation" to "governance and scale." Writing about the intersection of code, policy (EU AI Act), and automation.

TL;DR: OpenAI's Model Context Protocol and Google's Project Mariner deliver universal data pipes and browser automation. Learn how to build AI workflows fast.

Quick Take: OpenAI's Model Context Protocol and Google's Project Mariner deliver universal data pipes and browser automation APIs. These tools eliminate custom RAG pipelines and brittle Selenium scripts, shifting competitive advantage to domain expertise and workflow design.

MCP + Mariner: The Two APIs Every Builder Should Watch

Model Context Protocol—"USB-C for AI"

MCP is an open protocol that standardizes how apps feed tools and data into large language models. Think: OAuth + schema for files, emails, tickets, or even Salesforce records via community connectors, github.com. OpenAI just enabled free Gmail, Drive, Outlook, Dropbox connectors inside ChatGPT—no plug-in install needed.

Builder angle: Instead of writing bespoke RAG pipelines, drop an MCP connector and let ChatGPT search, summarize, or transform data in your SaaS with one prompt. Expect a cottage industry of niche connectors (e.g., Jira sprints, SAP ledgers) by the end of Q3.

Project Mariner—Agents That Click for You

Unveiled at Google I/O 2025, Mariner exposes a Computer Use API letting Gemini agents navigate browsers, fill forms, and juggle up to 10 simultaneous tasks. Early testers (Automation Anywhere, UiPath) are wiring Mariner into RPA flows; broader Gemini API access lands this summer.

Builder angle: Replace brittle Selenium scripts with an LLM that sees the DOM and adapts. Use Mariner's Teach & Repeat to demo a workflow once—agents will replicate it at scale.

Why both APIs shift strategy

Pain PointOld WayNew Way
Data silosBuild a custom ETL or RAG for each sourcePlug an MCP connector; prompt "Search last Q's invoices"
Web automationHeadless browser + XPath headachesMariner agent navigates dynamically, retries, explains
Multi-tool orchestrationChain scripts & webhooksOne agent calls MCP (data) + Mariner (action) in a loop

Takeaway: The moat moves to domain depth and workflow UX. If your startup only connects data or clicks buttons, these APIs will undercut you. Innovate on insight, analytics, or compliance on top.

Tool Highlight — Vertex AI Agent Builder

Just announced, Google Cloud's Agent Builder sits on top of Mariner and Gemini APIs—drag-and-drop UI to orchestrate multi-agent flows without redeploying your stack. Great for internal automation prototypes before you commit code.

Fun Fact—The First Public Web API Was for… a SOAP Bar?

Not quite—but close. Salesforce launched the first enterprise web API in February 2000 so developers could integrate "Sforce" CRM data into apps over XML-RPC (pre-REST). Twenty-five years later, we're wiring entire browsers into LLMs—proof APIs age like fine wine (with occasional SOAP-y residue).

Wrap-Up & CTA

MCP and Mariner hand you universal data pipes and browser automation. Question: Which will you prototype first—a connector-powered insight bot or a Mariner form-filler? Hit reply and share; your experiments fuel tomorrow's deep dive.

Until next time—keep prompts sharp and endpoints secure.


Originally published at First AI Movers. Written by Dr. Hernani Costa, Founder and CEO of First AI Movers.

Subscribe to First AI Movers for daily AI insights and practical automation strategies for EU SME leaders. First AI Movers is part of Core Ventures.

Ready to automate your business? Book a call today!