Skip to main content
Glama
menoxz

brave-mcp

by menoxz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to brave-mcp

No user-submitted related servers found.

    Related Servers

    • browser-mcp

      The-Syntax-Slayer
      A
      license
      Not graded
      quality
      B
      maintenance
      Unified MCP server for browser automation (Playwright + CDP + CLI) and bookmark management across Chrome, Firefox, Edge, and Brave, including cross-browser sync, deduplication, and a React dashboard.
      1
      MIT

    • chrome-mcp

      wzxklm
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.
      149 npm
      2
      MIT

    • chrome-devtools-mcp-wrapper

      CornWorld
      A
      license
      Not graded
      quality
      C
      maintenance
      Shares one Chrome browser across multiple AI coding sessions via an MCP proxy, adding lifecycle management, tool filtering, and anti-detection while wrapping the upstream chrome-devtools-mcp server.
      1 npm
      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.1/5.0

    Scored across 34 tools

    Disambiguation3/5

    Several tools have overlapping purposes: fill, fill_form, and type_text all handle text input; browser_launch and browser_restart are nearly identical; browser_list and browser_status both report on browser state. While descriptions provide some clarification, an agent could easily misselect between these pairs.

    Naming Consistency3/5

    The majority of tools follow a verb_noun pattern (list_pages, close_page, take_screenshot, navigate_page), but several browser management tools reverse this (browser_list, browser_launch, browser_status) and some tools are single verbs (click, hover, fill, drag). The mixed ordering and occasional vague names (emulate) create an inconsistent but still readable pattern.

    Tool Count2/5

    With 34 tools spanning page interaction, form handling, performance tracing, network/console inspection, and browser management, the server is heavily overloaded. While the domain is broad, the count exceeds the 25+ threshold and many tools could be consolidated (e.g., merging fill and type_text, or combining browser_list/status).

    Completeness4/5

    The toolset covers a comprehensive browser automation lifecycle: navigation, page selection, interaction, form filling, file upload, screenshots, snapshots, performance traces, and network/console inspection. Minor gaps include lack of explicit cookie management or request interception, but these can be worked around via evaluate_script.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources