Overview
Rindler is infrastructure that lets AI agents use real websites more reliably. It maps websites, tests those mappings against the live site, and exposes the result through a hosted MCP server. An agent can then search, pull structured records, fill forms, submit flows, or hand off a cart without relying on raw HTML scraping or brittle selectors.
This is a timely tool for the AI agent market because many agents still fail when they leave a clean API and enter a messy website. Rindler's public FAQ describes a hosted MCP server at mcp.rindler.ai with tools such as start_session, dispatch_action, extract_content, and close_session. The supported clients include ChatGPT, Claude, Claude Code, Cursor, Devin Desktop, Codex, and other MCP-capable agents.
Rindler is not just another AI web scraping service. Its pitch is that agents get structured, deterministic records and action capabilities, while authentication, navigation, retries, and error recovery run server-side. That makes it relevant to developer teams building agent workflows that must operate existing third-party websites.
Key Features
Hosted MCP server - Connects MCP-capable agents to Rindler's website automation layer without a custom client library or per-client SDK.
Structured extraction - Returns typed records instead of raw DOM dumps, which can reduce token load and make agent outputs easier to validate.
Website actions - Supports tasks such as searching, filtering, filling forms, downloading records, submitting workflows, and cart handoff.
Login-aware sessions - Designed for websites that require sign-in, with authentication and session management handled outside the agent prompt.
Self-healing mappings - Rindler says site mappings adapt when layouts change and are verified against the real site.
Developer setup path - The FAQ documents an installer command and OAuth-based authentication for MCP clients.
Pricing & Plans
Rindler's public FAQ has shown pricing language that changed across crawled versions. The current crawled FAQ text includes Starter at $100/month after a 7-day free trial, Teams at $1,000/month, and quoted Enterprise agreements. It also describes one successful session as one credit.
Because pricing has been in motion, teams should confirm the live pricing page before procurement. For this listing, the starting public paid price is recorded as $100/month.
| Plan | Price | Notes |
|---|---|---|
| Starter | $100/month | 7-day free trial, 100 credits/month, one custom site mapped and maintained |
| Teams | $1,000/month | 1,000 credits/month, more public sites and one login-gated site mapped |
| Enterprise | Custom | More sites, burst capacity, onboarding, and production agreements |
Best For
- Agent builders who need a managed web action layer instead of raw browser control
- Developers connecting ChatGPT, Claude, Codex, Cursor, or other MCP clients to live websites
- Teams automating login-gated portals, record downloads, status checks, and form submissions
- Products that need structured web records rather than screenshots or raw HTML
- Companies comparing browser automation against AI workflow generator platforms
FAQ
What is Rindler?
Rindler is hosted web automation infrastructure for AI agents. It turns websites into structured MCP tools that agents can call to search, extract, fill forms, and complete workflows.
Does Rindler use MCP?
Yes. Rindler exposes a hosted MCP server at mcp.rindler.ai, so compatible agents can call tools over the Model Context Protocol.
Which agents work with Rindler?
The public FAQ names ChatGPT, Claude, Claude Code, Cursor, Devin Desktop, Codex, and other MCP-capable clients.
How much does Rindler cost?
The reviewed FAQ lists Starter at $100/month after a 7-day free trial, Teams at $1,000/month, and Enterprise as custom. Confirm live pricing before purchase because the public pricing language has changed.
Is Rindler the same as scraping?
No. Rindler focuses on structured records and website actions through a maintained MCP layer, while traditional scraping usually extracts raw page content through selectors or browser scripts.
Can Rindler handle login-gated websites?
Yes, login-aware sessions are part of the product's positioning. Teams should still test their exact target sites, authentication flows, and permission model before production use.
