Node Mantis
OfficialRelated Servers
Alternatives to Node Mantis
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to browse websites, extract information, fill forms, interact with pages, and execute multi-step web tasks autonomously.-
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to drive a real browser against sites that publish no API — search forms, logins, multi-step lookups — then poll for the extracted result or cancel a run. Runs take seconds to minutes, are billed per browser step to the user's own account, and return structured output or a failure reason rather than throwing.336 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.63MIT

Cloak Agentofficial
AlicenseAqualityBmaintenanceEnables an agent to run whole browser tasks on live web pages from a plain-language goal — opening tabs, clicking, typing, scrolling, and returning the relevant page sections as markdown — with every step reported alongside its confidence. Tabs can be reused and closed across calls, so multi-step flows continue on the page the previous task ended on.26MIT- AlicenseAqualityCmaintenanceEnables AI-powered web browsing automation using Google's Gemini 2.5 Computer Use API. Allows agents to navigate websites, click buttons, fill forms, and extract information through natural language commands with real-time progress tracking.7MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.Apache 2.0
TDQS
Scored across 4 tools
Each tool owns a distinct action in the browser-task lifecycle: start an acting task, start a read-only extraction, wait on a task, and cancel a task. The descriptions explicitly resolve the one risky boundary (run_task vs retrieve_data) by telling the agent to prefer run_task when navigation or multiple pages are needed.
All four names follow a consistent snake_case verb_noun pattern (run_task, retrieve_data, get_task, cancel_task). The shared _task suffix on the task-lifecycle tools reinforces the pattern and makes relationships visible.
Four tools is tight and well-scoped for a browser automation server: two entry points for starting work and two for managing in-flight tasks. Nothing feels redundant or missing at the naming level.
The async lifecycle is fully covered (start, poll, cancel) plus optional result_schema shaping for output. Minor gaps remain: there is no way to list or enumerate outstanding tasks/task_ids, and the absence of session persistence means logins and multi-step flows can never be resumed across calls.