Skip to main content
Glama
ashley-ha

MCP Browser Agent

by ashley-ha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Browser Agent

No user-submitted related servers found.

    Related Servers

    • Browser Agent MCP

      imprvhub
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.
      13
      8
      41
      TypeScript
      Mozilla Public 2.0

    • Claude Chrome MCP

      nonsleepr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT

    • Browser MCP Server

      Akioo77
      A
      license
      A
      quality
      C
      maintenance
      A browser automation tool using Playwright and MCP protocol, enabling agents like OpenClaw or Claude Desktop to control a browser for navigation, content extraction, and interaction.
      21
      6
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: get_planner_state retrieves browser state and planning context, while execute_actions performs actions based on that state. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with clear action-oriented names (get_planner_state, execute_actions). The naming convention is uniform and predictable throughout the set.

    Tool Count2/5

    With only 2 tools for a browser automation server, the surface feels severely limited. While the tools cover a basic planning-execution loop, typical browser automation requires more granular operations like navigation, element interaction, or content extraction.

    Completeness2/5

    The toolset provides only a high-level planning/execution abstraction without direct browser manipulation capabilities. There are significant gaps for common browser tasks like navigating to URLs, clicking elements, extracting text, or handling dialogs, which agents would need for robust automation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources