Skip to main content
Glama
afreakk

qutebrowser-mcp

by afreakk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to qutebrowser-mcp

No user-submitted related servers found.

    Related Servers

    • camofox-browser-mcp

      Microck
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for controlling a local camofox-browser instance, enabling LLM agents to perform web automation tasks such as navigation, interaction, snapshotting, and content extraction.
      17 npm
      MIT

    • bwb-browser-termux

      krshforever
      A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight browser automation MCP server using raw Chrome DevTools Protocol, enabling web navigation, screenshots, and DOM interaction without heavy dependencies, and working on Termux/Android.
      1,374 npm
      MIT

    • mcp-chromium-cdp

      duquesnay
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Chromium/Chrome via Chrome DevTools Protocol. Supports cross-platform automation, auto-launch, and automatic reconnection.
      25
      1
      MIT
    • sendblue-browser by sendblue-api

      sendblue-browserofficial

      sendblue-api
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that wraps sendblue-browser-use's HTTP API, providing tools to control a stealth-patched Chromium browser with persistent sessions, navigation, screenshots, and script execution.
      3
      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

    A4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: tab management, navigation, bookmarks/history, and fetch operations are all separate. Even the two fetch tools are differentiated by their auth mechanisms, and navigation tools like navigate, go_back, go_forward, and reload_page target different actions.

    Naming Consistency5/5

    All tools follow a consistent lowercase snake_case verb_noun pattern (e.g., list_tabs, open_tab, close_tab, search_history). Even the phrasal go_back and go_forward fit the pattern, and browser_fetch/browser_fetch_auth are verb_noun compound names that remain consistent.

    Tool Count4/5

    At 16 tools, the set is slightly over the ideal 3-15 range, but each tool serves a distinct function and covers a broad browser automation domain. The additional fetch and auth tools justify the count without feeling redundant.

    Completeness4/5

    The server covers core tab lifecycle, navigation, bookmarks/quickmarks, history search, screenshots, JS execution, and authenticated fetching. Minor gaps like missing tab pinning or direct URL retrieval are workable around via list_tabs, so the surface is strong overall.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources