Use case · Coding agents
Your agent can click through a site.Now it can leave a program behind.
Coding agents are good at exploring a site and bad at doing it the same way twice. With Kaabist over MCP, the agent explores in a real browser, and what it learns becomes a fixed program that runs the same way every time, without the agent.
The problem
An agent that drives a browser on every run is slow, costs tokens each time, and takes a slightly different path every time. That is fine for exploring, and wrong for anything you run on a schedule.
How it works
01
Explore with the agent
Connect your agent to mcp.kaab.ist. It opens a Kaabist browser, reads a condensed view of each page, and acts on ranked locators instead of guessing at selectors.
exampleclaude mcp add --transport http kaab https://mcp.kaab.ist/mcp
02
Keep what worked
The agent turns its session into a draft program, lints it, and dry-runs it. You review the program, not a transcript.
03
Run it without the agent
The published program runs on Kaabist, on a schedule or from your API calls, the same way every time. The agent is only needed again when you want to change it.
Questions
Askedbefore you ask.
More use cases
Scrape a website that requires login
Portals, dashboards, supplier sites: the data you need sits behind a sign-in form. Kaabist runs the login as part of a program, keeps the session between jobs, and reads the pages as typed, validated fields.
Automate logins with 2FA
One-time codes by e-mail or SMS, authenticator prompts, approval screens: a second factor is a step only the account owner can finish. Kaabist pauses the job there, emails a link to you (or the teammate or customer who owns the account), and resumes the program the moment the code is typed.
Forms that must submit exactly once
Some forms change the world when they are sent: an order is placed, money moves, an application is filed. Kaabist records those steps just before and just after they run (a fence), so a crash, a retry or a redeploy can never send them twice.