Skip to main content
Glama
OpenSWE

jev-browser-use-mcp

by OpenSWE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jev-browser-use-mcp

No user-submitted related servers found.

    Related Servers

    • webverb-mcp

      cs0317
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to perform typed, site-specific actions across a signed-in Chrome browser, interacting with services like Gmail, Reddit, Drive, and Amazon through natural language requests.
      1
      MIT

    • browser-mcp

      JuntongLiu96
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives coding agents full control over a real Chrome browser, enabling navigation, clicking, typing, screenshotting, and more via an MCP server and Chrome extension.
      16 npm
      2
      MIT

    • Agentic Browser

      applejuice093
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to control a real Chromium browser with semantic tools, providing compact observations and outcome-verified actions for web interaction tasks.
      1
      MIT

    • chrome-mcp

      predotdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any coding agent to use the user's existing Chrome profiles and logins to open tabs, read pages, fill forms, click through flows, and take screenshots.
      1,430 npm
      MIT

    • voltcrawl

      adi-IL
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to retrieve verified web evidence via headless Chromium rendering, sitemap navigation, and search candidate discovery, returning clean Markdown, structured JSON, and verbatim quoted proof.
      3 npm
      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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct responsibilities: one drives and continues browser sessions, the other closes them. There is no overlap or ambiguity between starting/continuing work and cleaning up a session.

    Naming Consistency5/5

    Both names follow a consistent verb_noun snake_case pattern with the browser prefix: run_browser_task and close_browser_session. The naming is predictable and easy to reason about.

    Tool Count3/5

    Two tools is on the thin end, but run_browser_task intentionally subsumes a broad range of browser actions through a goal-based interface. It is reasonable for a minimal server, though the surface feels slightly limited.

    Completeness4/5

    The core browser-use lifecycle is covered: start a task, continue/redirect it, and close the session. Minor gaps exist, such as no explicit session listing or status tool, but the natural-language task abstraction covers most practical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources