Skip to main content
Glama
CapMonsterCloud

Capmonster MCP Browser Automation

Official
by CapMonsterCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Capmonster MCP Browser Automation

No user-submitted related servers found.

    Related Servers

    • Thunder

      emmanuelerogian723-alt
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to drive a stealth browser with human-like mouse and keyboard behavior, fetch pages with browser-true TLS, route screenshots to vision models, detect and bridge CAPTCHA challenges, and obtain structured next-action plans from local or remote models through MCP.
      15
      MIT

    • CamoFox MCP

      keithrezende
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to automate the web through an anti-detection browser, supporting navigation, interaction, search, extraction, downloads, multi-tab workflows, and session reuse.
      971 npm
      MIT

    • cdp-browser-mcp

      killaragorn
      A
      license
      B
      quality
      B
      maintenance
      MCP server that attaches to already-running Chromium browsers via CDP, enabling agents to control multiple browser sessions for navigation, input, network capture, and automation while avoiding anti-bot detection with Patchright.
      26
      20 npm
      1
      MIT

    • Real Browser MCP

      qxZap
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a real browser that bypasses bot detection (Cloudflare, Turnstile) for AI agents, enabling navigation, clicking, typing, screenshots, and data collection through MCP tools.
      497 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 66 tools

    Disambiguation3/5

    Most tools fall into clear categories (navigation, input, storage, network), but several pairs overlap: browser_run_code_unsafe duplicates browser_evaluate, and browser_iframe_click/browser_iframe_fill are legacy shorthands for browser_click/browser_fill with frameSelector. The detailed descriptions mitigate confusion, so boundary issues are limited to a handful of cases.

    Naming Consistency4/5

    All tools share a consistent browser_ prefix and most follow a verb-object or area-action pattern (cookie_get, storage_save, navigate, click). However, some query tools are noun-named instead of verb-named (browser_status, browser_pages, browser_network_requests) and browser_new_page breaks the verb pattern, so it is not fully uniform.

    Tool Count2/5

    66 tools is far beyond the 3-15 sweet spot and well past the 25+ threshold for too many, making the server heavy for an agent to navigate. The tools are at least organized into coherent families, but the sheer number and 15 near-identical CRUD micro-tools for cookies/localStorage/sessionStorage inflate the surface.

    Completeness3/5

    The browser automation surface is extensive, covering navigation, input, network interception, storage, and passkeys, with only minor browser gaps like reload/forward/scroll. However, the server is branded capmonster and browser_save_blob explicitly references create_task, yet no CapMonster task-creation or result-retrieval tools exist, leaving a notable dead end for the intended captcha workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources