octolimb
Related Servers
Alternatives to octolimb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to drive a live Chrome or Brave browser over stdio, with tools for navigation, clicking, typing, screenshots, and executing automation goals.4MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control Chrome reliably over MCP, including multi-tab browsing, forms, clicks, keyboard, scrolling, drag, uploads, downloads, dialogs, JavaScript evaluation, and console/network inspection, in headed or headless mode or attached to an existing Chrome instance.2213 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.251MIT
- AlicenseAqualityCmaintenanceEnables coding agents to drive a real, indexed Chrome browser over MCP stdio, navigating pages, observing numbered interactive elements, and performing click, type, and select actions without the server itself calling any model.5MIT
- AlicenseNot gradedqualityDmaintenanceHosted Chrome as an MCP skill. Enables any MCP-compatible agent to drive a real Chromium browser for tasks like navigation, clicking, typing, and taking screenshots.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a real Chrome browser over MCP, with each agent's tabs organized into task-named tab groups. Agents can read pages as compact outlines with element refs, then click, fill, press keys, upload files, run JavaScript, capture screenshots and inspect console/network logs.MIT
TDQS
Scored across 24 tools
Most tools target clearly distinct browser actions, and the descriptions explicitly distinguish tab-scoped navigation from browser history (go_back) and scrolling. There is some potential overlap between scroll variants and pagination tools, and execute_js could be seen as a catch-all alternative, but the intended boundaries are mostly clear.
Nearly all names use readable snake_case, and action tools generally follow verb_noun or verb patterns. Minor deviations include one-word controls like done and wait, and noun-only names like previous_page and next_page, but the set remains predictable overall.
At 24 tools, the set is on the heavy side for a browser automation server and includes several granular scroll and tab primitives that could be consolidated. However, each tool does correspond to a real browser operation, so the count is not entirely unjustified.
The surface covers core browser workflows: navigation, inspection, clicking, text input, scrolling, tabs, dropdowns, JavaScript execution, and recipe replay. Some gaps remain, such as explicit hover, drag-and-drop, file upload, screenshots, or forward navigation, but these are relatively minor for many tasks.