Skip to main content
Glama
zc-libre

camoufox-mcp-python

by zc-libre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to camoufox-mcp-python

No user-submitted related servers found.

    Related Servers

    • camoufox-mcp

      ccostello97
      A
      license
      B
      quality
      D
      maintenance
      Browser automation MCP server using Camoufox anti-detect browser with fingerprint spoofing, geolocation/timezone spoofing, and human-like cursor movement.
      14
      1
      Apache 2.0

    • Camoufox MCP

      LowOrbitLab
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for authorized browser automation using Camoufox, managing multiple tabs and providing 21 browser tools for interaction.
      -

    • 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
      34 npm
      7
      MIT

    • Playwright Server

      williamvd4
      A
      license
      B
      quality
      Not graded
      maintenance
      A MCP server that provides browser automation tools, allowing users to navigate websites, take screenshots, click elements, fill forms, and execute JavaScript through Playwright.
      8
      2
      Apache 2.0

    • camofox-browser-mcp

      Microck
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for controlling a local camofox-browser instance, enabling LLM agents to perform web automation tasks such as navigation, interaction, snapshotting, and content extraction.
      16 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct interaction or observation (e.g., click vs. hover vs. drag, type vs. press_key vs. fill_form). The only mild overlap is between type and fill_form, but their descriptions clearly scope them to single-element vs. multi-field actions. Overall, no two tools are easily confused.

    Naming Consistency4/5

    All tools share the 'browser_' prefix, creating a strong family resemblance. However, the suffix pattern is mixed: some are verb-first (browser_click, browser_navigate) while others are resource-first (browser_tabs, browser_console_messages, browser_network_requests). Despite this, the prefix and clear action descriptions make the naming predictable.

    Tool Count4/5

    At 19 tools, the set is slightly above the typical 3-15 range but well-justified for a comprehensive browser automation server. The count covers navigation, input, observation, and tab/window management without feeling redundant. A few tools could theoretically be combined (e.g., screenshot modes), but the granularity is reasonable.

    Completeness5/5

    The tool surface covers the core browser automation lifecycle: navigation (navigate, back), interaction (click, hover, drag, select, type, press_key, fill_form), waiting (wait_for), and introspection (snapshot, console, network, screenshot). It also handles dialogs, file uploads, tabs, resize, and closing, leaving no obvious dead ends for standard automation scenarios. Advanced features like JS evaluation are absent but not essential for basic browser control.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources