Skip to main content
Glama
ccostello97

camoufox-mcp

by ccostello97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to camoufox-mcp

No user-submitted related servers found.

    Related Servers

    • Camoufox MCP

      baixianger
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for anti-detection browser automation that uses Camoufox to bypass bot detection and spoof digital fingerprints. It enables AI agents to perform human-like web interactions, including realistic cursor movements, humanized click delays, and automatic cookie popup dismissal.
      36
      21
      7
      MIT

    • invisible-playwright-mcp

      LowOrbitLab
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server exposes an anti-detect Firefox browser that passes bot-detection tests, allowing LLMs to automate web interactions with humanized clicks and fingerprint randomization.
      MIT

    • Chrome MCP Stealth

      Riaan-Fourie
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for stealth browser automation that uses human-like interaction patterns to bypass bot detection via the Chrome DevTools Protocol. It enables users to navigate, interact with elements, and capture data from websites using undetectable behaviors like Bezier mouse movements and Gaussian typing delays.
      149
      1
      MIT

    • camoufox-mcp-python

      zc-libre
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that provides browser automation with anti-detect fingerprinting, accessibility snapshots, and ref-based element targeting, powered by Camoufox.
      19
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct action: navigate, snapshot, click, type, fill, hover, select, key press, wait, evaluate, screenshot, tabs, back, close. The only potential overlap is type vs. fill, but descriptions clarify that fill clears first, making them distinct.

    Naming Consistency5/5

    All tools use the 'browser_' prefix followed by a verb_noun pattern (e.g., browser_navigate, browser_click, browser_screenshot). The naming is predictable and uniform, with only minor deviations like browser_wait_for (verb_preposition) and browser_tabs (verb_noun but plural) that are still clear.

    Tool Count5/5

    14 tools is an ideal size for a browser automation server. It covers all essential interactions without being bloated. Each tool serves a specific purpose and there are no redundant or unnecessary tools.

    Completeness4/5

    The tool set covers the core browser automation lifecycle: navigation, interaction, tab management, screenshots, and JavaScript evaluation. Minor gaps exist, such as the absence of navigate_forward (only back) and a dedicated wait-for-element function (only wait for text or time). These are small but notable omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources