Skip to main content
Glama
dawgswarm

dawg-mcp

by dawgswarm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dawg-mcp

No user-submitted related servers found.

    Related Servers

    • Camoufox Unified MCP Server

      tom613951
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.
      MIT

    • Browserbase MCP Server

      madaoQ
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides cloud browser automation capabilities for AI agents, including creating, managing, and retrieving recordings and logs from browser sessions.
      MIT

    • personae

      leek-emperor
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control isolated Chromium browser identities, allowing per-account navigation, interaction, and inspection through MCP without requiring Node or CLI installation.
      2
      MIT

    • Reasonix Browser Bridge

      liutingqiu
      A
      license
      Not graded
      quality
      A
      maintenance
      Browser automation for AI agents: tabs, cookies, arbitrary JS execution (via CDP, bypasses CSP), screenshots, downloads, proxy switching, data cleanup. Chrome & Edge multi-browser, full permissions, zero configuration. 25+ MCP tools.
      1
      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

    A3.5/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each browser_ tool has a distinct action (navigate, click, type, screenshot, etc.) and each scrape_ tool has a distinct purpose (single page, batch, crawl, status). The only potential overlap is between browser_snapshot and browser_take_screenshot, but they serve different use cases (interaction vs visual verification). Overall, tools are clearly differentiated.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: browser_* for browser operations and scrape_* for scraping operations. All use snake_case. No mixing of conventions, making it predictable and easy to understand.

    Tool Count4/5

    24 tools is on the higher side but still reasonable for a server that combines browser automation and web scraping. Each tool serves a clear purpose, and the count is justified by the breadth of functionality. Could be reduced slightly, but not overwhelming.

    Completeness4/5

    The browser tools cover most common actions (navigation, clicks, form filling, tabs, screenshots, session management). The scraping tools provide single page, batch, and crawl operations with status checks and cancellation. Missing some advanced browser features (e.g., file upload, iframe handling), but the core workflows are well-covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources