Riffle vs Agent Browser
A side-by-side look at the Riffle and Agent Browser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RiffleBrowser AutomationYour agent uses the web as text, not screenshots. Several steps per call, only changes come back.37FairAuth: no auth requiredVerdict: choose Riffle for browser automation work; choose Agent Browser for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
RChoose Riffle when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
Choose Agent Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Riffle | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 37/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Riffle tools
No tool names declared yet. Check the project README from the listing page.
Agent Browser tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Riffle
No confirmed install command for Riffle yet — follow the setup steps linked from its listing page rather than a guessed package name.
Agent Browser
{
"mcpServers": {
"agent-browser": {
"command": "npx",
"args": [
"-y",
"aether-browser"
]
}
}
}
Frequently asked questions
Riffle is categorized under Browser Automation and uses an install path we have not confirmed yet. Agent Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Riffle for browser automation work and Agent Browser for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Riffle has no confirmed install command yet — follow its own setup instructions.
Riffle is listed as free. Auth: no auth required. Agent Browser has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add riffle and agent-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Riffle has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. Agent Browser has 44/100 (Fair) with 0 views, 0 installs and 12 GitHub stars.
