Skip to main content
Glama
jfjensen

camofox-browser MCP server (stage2)

by jfjensen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to camofox-browser MCP server (stage2)

No user-submitted related servers found.

    Related Servers

    • dev-browser-mcp

      kamkozlowski
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to control a persistent Chromium browser or attach to an existing Chrome with sandboxed JavaScript and structured tools for web interaction and automation.
      16
      MIT

    • browserpilot

      RAGEFULRHINO16
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to control an existing Chromium browser or isolated Playwright profile through 50 tools for reading, interacting with, navigating, capturing, transferring files, and coordinating tabs, with per-site permissions and one-use approvals.
      4
      MIT

    • MCP-RealBrowser

      obbbba
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent browser profile for AI agents, enabling them to log in once and maintain sessions across restarts. Supports 20 tools for browsing, navigation, text extraction, and screenshot.
      1
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A4.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a distinct purpose: interactions (click, type_into, press_key, select_option), tab management (open, close, read), and content retrieval (fetch_snippet, summarize, extract, fetch_urls, fetch_structure, plus tab variants). No ambiguity between tools.

    Naming Consistency5/5

    Names follow a predictable verb_noun pattern (e.g., open_tab, close_tab, read_tab, fetch_snippet, summarize_tab). Single-word verbs like click and extract are acceptable as they are common actions. The convention is consistent throughout.

    Tool Count5/5

    15 tools cover the full scope of browser automation: tab lifecycle, element interaction, multiple reading methods (snippet, summary, extract, structure, links). The count is well-balanced, not excessive or sparse.

    Completeness4/5

    Covers core browsing operations thoroughly: open/close tabs, interact with elements, read pages in various ways, extract structured data. Missing explicit navigation history or tab listing, but these can be managed externally. Minor gap, overall solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources