Skip to main content
Glama
nvk

llm-wiki-chrome

by nvk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llm-wiki-chrome

No user-submitted related servers found.

    Related Servers

    • browser-relay by Wecko-ai

      browser-relayofficial

      Wecko-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that drives a user's real Chrome browser via a WebSocket-connected MV3 extension, enabling tab management, navigation, page interaction, screenshots, and script evaluation through natural language.
      3 npm
      MIT

    • browser-mcp

      huaka1
      A
      license
      A
      quality
      D
      maintenance
      Agent-native browser control MCP server that enables AI agents to browse and interact with web pages via accessibility tree snapshots and ref ID-based commands.
      15
      2
      MIT

    • Echo

      krishngohel
      A
      license
      Not graded
      quality
      A
      maintenance
      Local browser MCP server that lets AI assistants control a real desktop browser via tools like navigate, snapshot, and search_web.
      MIT

    • mcp-server-agent-browser

      codeChap
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that wraps agent-browser to let LLMs control a real browser, providing tools for navigation, interaction, reading page content, accessibility snapshots, screenshots, and session management.
      1
      -

    • chrome-agent-bridge

      escapeWu
      A
      license
      C
      quality
      A
      maintenance
      MCP server for agent interaction with user-approved Google Chrome tabs, enabling tab listing/control, navigation, clicking, filling, snapshots, and screenshots via a local authenticated bridge.
      96
      2
      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

    B3.2/5.0

    Scored across 34 tools

    Disambiguation5/5

    Every tool targets a distinct browser action, from navigation and interaction to recording and scheduling. Detailed descriptions clearly differentiate similar operations like screenshots vs. snapshots, making confusion unlikely.

    Naming Consistency5/5

    All tools follow the browser_verb or browser_verb_noun pattern in lowercase snake_case, with no mixing of conventions. The naming is predictable and uniform across all 34 tools.

    Tool Count4/5

    34 tools cover a wide range of browser automation tasks, including diagnostics, recording, and scheduling. While on the higher side, each tool serves a distinct purpose and the count is reasonable for the domain's scope.

    Completeness4/5

    The tool set covers core browser workflows: navigation, interaction, screenshot, form handling, upload/download, and tab management. Minor omissions like direct JavaScript execution or page source retrieval are likely intentional for security, so the surface is well-scoped for its constrained environment.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources