botcan-mcp
Related Servers
Alternatives to botcan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to launch a fingerprint-randomized browser, navigate, click, type, read the DOM, and take screenshots through a patched Firefox engine.MIT
- AlicenseNot gradedqualityAmaintenanceTurns YAML-defined browser flows into typed MCP tools that Claude, Cursor, VS Code and other MCP clients can call, letting agents run repeatable tasks like logins, form fills, report downloads, price checks and data extraction without letting them wander the page freely. Each call returns JSON output, downloaded files or screenshots, and failures report the step, error, page URL and a screenshot.0MIT
- AlicenseAqualityBmaintenanceEnables web search and browser automation against a real, locally installed Firefox driven over its built-in Marionette TCP protocol. Exposes tools for multi-engine search, JS-rendered page text and link extraction, screenshots, cookie save/load, and arbitrary JS evaluation, with SSRF guarding, rate limiting, and untrusted-content wrapping.10MIT
- AlicenseNot gradedqualityAmaintenanceExposes a 47-tool browser automation surface to MCP clients, enabling AI agents to navigate, interact with, observe, and extract content from web pages across multi-tab sessions. Runs on Camoufox-based anti-detection behavior so agents can automate sites that block conventional headless browsers, with session persistence, cookie import, and stdio or HTTP transport.971 npmMIT
- AlicenseBqualityAmaintenanceLet AI agents use the Firefox, Zen, or LibreWolf browser you already have open, with your logins, cookies, and extensions intact. No Playwright, Chromium, or WebDriver. Agents work in background tabs while you keep browsing: read pages, click, fill forms, take screenshots, and capture network traffic. A WebExtension plus a local bridge lets several agents share one browser.259MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a local Firefox browser: opening and managing tabs, navigating, reading page structure and text, clicking, typing, filling forms, running JavaScript, taking screenshots, and inspecting console messages and network requests. Everything runs over a local Unix socket with no network traffic, and actions are restricted to tabs explicitly placed under Claude's control.2 npmGPL 3.0
TDQS
Scored across 2 tools
Both tools execute YAML recipes; the only difference is file vs inline string input. Descriptions clarify the distinction, but the core action overlaps, and the names play_recipe vs play_steps could confuse an agent about which to use.
Both tools follow a clear verb_noun pattern with the same verb 'play_', making the naming predictable and consistent throughout.
Only two tools are provided, which feels thin for a recipe execution server. While both earn their place, the set is borderline minimal for the apparent scope.
The surface covers file-based and inline execution, but notable operations like recipe validation, listing available recipes, or error handling without execution are missing. Agents can work around these gaps, but they are significant.