acrawl
Related Servers
Alternatives to acrawl
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceNative webview browser automation for AI agents. Rust-powered, with JSON-lines control and a built-in MCP server. Runs on macOS, Linux, and Windows.431MIT
- AlicenseNot gradedqualityBmaintenancesingle-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.14MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.-
- AlicenseNot gradedqualityDmaintenanceMCP server that bridges Model Context Protocol with browser automation, offering 37 tools across three modes (Playwright, CDP, Chrome Extension) and an autonomous agent for web tasks.MIT
- FlicenseNot gradedqualityAmaintenanceEnables any LLM agent to fetch, extract, crawl, and screenshot through conversation via 17 scraping tools over stdio or SSE, letting an agent run a full crawl end-to-end. Works with Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT, LangChain, and the OpenAI Agents SDK.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the web through an anti-detection browser backend, with 47 tools for navigation, interaction, observation, search, extraction, downloads, and session reuse. Supports multi-tab workflows, persistent profiles, cookie import, and HTTP or stdio transports for MCP-compatible clients.971 npmMIT
TDQS
Scored across 40 tools
Most tools have clearly distinct purposes: navigation, interaction, inspection, scripting, network, storage, and auditing are separated by action and resource. A few pairs need care (wait vs wait_for_scripts, execute_js vs run_script/run_goal, page_map vs read_content/list_resources), but descriptions clarify their boundaries.
Names are consistently snake_case and mostly follow a verb_noun or verb pattern. Deviations are mostly natural single-word browser actions (navigate, click, scroll, hover, refresh, wait) or noun-oriented views (page_map, script_status), so the convention remains readable overall.
With 40 tools, the surface is heavy for an agent to navigate and exceeds the reasonable 3–15 range despite the broad browser-automation domain. Many specialized inspection, auditing, and script-management tools could be consolidated or exposed through fewer parameterized tools.
Coverage is broad: navigation, interaction, forms, waits, scripts, network/WebSocket logs and interception, cookies/storage inspection, performance, accessibility, coverage, screenshots, device emulation, and autonomous goals are all represented. Minor gaps remain around cookie/storage mutation, explicit tab creation/closing, and file upload or dialog handling.