DEV Community

SoloAgentFlow
SoloAgentFlow

Posted on Originally published at soloagentflow.com

Pomerado Review: Turn Any Website Into an MCP in Under an Hour

Per the founders' Launch HN post. Pomerado is a new YC company.

Most automation projects for small businesses stall at the same spot: the one system the client depends on has no API. It is a dealer portal, an insurance site, a booking backend from 2009. Pomerado offers a way through. You describe a task, its agent completes it on the website once, and you get back an MCP tool your agent can call again and again.

In short

  • Pomerado turns a website task into an MCP in less than an hour, per the founders.
  • Later tool calls usually return in 5-30 seconds because runtime is deterministic, not computer use.
  • There is an MIT open-source version and a free hosted version.
  • Best fit: repeated, high-volume tasks on portals that have no API.

Why Agents Get Stuck on Ordinary Websites

The founders, Alan and Akshay, say they found the problem while building their own personal assistants. When they asked agents to book flights, the agents fell back on computer use and failed at checkout. Repeated workflows, like searching many airlines at once, made the problems worse.

They also bring enterprise context. According to the founders, they previously drove agent deployments in healthcare, professional services and telecom at McKinsey and Scale AI, and every time the biggest bottleneck was getting agents to work with legacy websites and apps.

How Pomerado Builds a Tool

1. One example run

Pomerado's agent opens a browser, explores the site and performs your task once by writing HTTP requests or a Playwright script. If it needs a login or a clarification, it asks you over MCP.

2. Generalize, guard and test

The agent uses that run and everything it recorded to build a repeatable API. A separate Guardian model reviews the coding agent's calls against guardrails. Pomerado then runs tests with synthetic inputs so the API is not overfit to one example, and a publication agent sets a sensible input and output schema.

3. Handle logins and 2FA

Sign-in is handed to a deterministic process so that, per the founders, neither the model nor their recorders read customer credentials. You can store 2FA TOTP seeds or link your account to a Pomerado phone number so it can fill in 2FA codes.

4. Self-heal when the site changes

If a later run fails, a maintenance job repairs the tool. It can fix a broken step such as a renamed button, add features such as business-class search on top of economy, or add guardrails such as requiring future reservation dates.

Computer Use vs Pomerado vs a Real API

Approach Setup Each run Best for
Computer use / live browser agent None Slow, costly, can fail mid-task; dealers in Pomerado's examples saw runs of 1 hour or more One-off or unpredictable tasks
Pomerado MCP Less than an hour per tool Usually 5-30 seconds, deterministic Repeated, high-volume tasks on sites without an API
Official API Depends on the vendor Fast and supported Anything where the vendor offers one

The practical rule: if an official API exists, use it. If the task is a one-time job, a live browser agent is fine. Pomerado earns its place in the middle, on the jobs you run every day on a site that will never ship an API.

Who Already Uses It

  • A personal trainer whose agents prepare workouts and message clients.
  • Car dealerships connecting Grok bots to legacy dealer systems, including marketplaces, CRMs and ERPs. They switched from computer use, which could take an hour or more.
  • Personal assistants integrating with a broad range of consumer websites.

A Risk Checklist Before You Build on It

  • Terms of service. Check whether the target site allows automated access, especially before you sell a connector to a paying client.
  • Credentials and money. Banking, insurance and airline accounts carry real risk. Add guardrails, such as limits on what a tool can submit.
  • Maintenance expectations. Self-healing reduces breakage, but a client will still ask why a run failed. Agree up front who watches failures.
  • Hosted vs self-hosted. The free hosted version is the quick start. The MIT open-source version suits clients who want data on their own infrastructure.
  • First-run time. Budget up to an hour for each new tool and test it on several inputs before it goes into a live workflow.

Steps to turn a website into an MCP

  1. List the repeated tasks that live on a website with no API.
  2. Pick one high-volume task and describe it in plain English.
  3. Choose the free hosted version for a quick test, or the open-source version if data must stay in-house.
  4. Let the agent complete the example run and answer its questions about login or edge cases.
  5. Test the resulting MCP with several realistic inputs and time each call.
  6. Add guardrails for anything that submits, pays or books.
  7. Connect the tool to your agent or workflow and track failures for the first two weeks.

Source: Launch HN: Pomerado (YC F26) - Turn any website into an MCP for agents

Originally published on SoloAgentFlow.

Top comments (0)