Skip to main content
Glama
halilc4

tabby-mcp

by halilc4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tabby-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Chrome Tools MCP Server

      nicholmikey
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.
      26 npm
      53
      MIT

    • paparazzi

      nicksenap
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects to your browser to capture screenshots, inspect console logs, network requests, and more via Chrome DevTools Protocol.
      3 npm
      2
      MIT

    • bwb-browser

      krshforever
      A
      license
      B
      quality
      A
      maintenance
      A lightweight 30KB MCP browser automation server that uses raw Chrome DevTools Protocol to enable AI agents to browse the web, take screenshots, interact with elements, and capture live page events like console logs and network requests.
      26
      7 npm
      15
      MIT

    • MCP Browser Logger

      tao-Lionel
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that captures browser console logs and network requests via the Chrome DevTools Protocol. It allows users to monitor real-time logs, inspect network traffic, and execute JavaScript code directly in the browser context.
      -
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: execute_js runs code, list_targets lists tabs, query finds DOM elements, screenshot captures images. There is no overlap.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (execute_js, list_targets), but 'query' and 'screenshot' are less consistent. Still, the pattern is understandable.

    Tool Count5/5

    Four tools is appropriate for a focused automation toolkit. Each tool serves a clear function without being excessive or insufficient.

    Completeness3/5

    The set covers basic inspection and execution but lacks common browser actions like navigation, clicking, or typing, which limits its completeness for typical automation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources