Skip to main content
Glama
hunglp97

tabpilot-mcp

by hunglp97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to tabpilot-mcp

  • Browser MCP

    Agent360dk
    A
    license
    A
    quality
    A
    maintenance
    Enables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.
    40
    44
    MIT

Related Servers

  • browser-mcp-cdp

    zhiqi-li
    A
    license
    A
    quality
    D
    maintenance
    Drives your real local Chrome with profile isolation, allowing LLMs to interact with your logged-in sessions without modifying your actual profile.
    13
    21 npm
    MIT

  • Fast Browser MCP

    kqlio67
    A
    license
    C
    quality
    A
    maintenance
    Enables AI agents and developers to automate real Chrome/Chromium browsers through the Chrome DevTools Protocol, with token-efficient snapshots, multi-action batching, shadow DOM traversal, system-page control, extension management, and network/WebSocket inspection.
    64
    MIT

  • Blinkwire

    81117105108108
    A
    license
    B
    quality
    B
    maintenance
    Provides fast, token-efficient browser automation for LLMs by attaching directly to a running Chrome instance via CDP, offering a full set of browser tools including navigation, interaction, and snapshot diffs, with batched actions to reduce round-trips.
    56
    GPL 3.0

  • Wbrowser

    matveikarpov64
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants and terminal users to control a logged-in Chrome browser, performing actions like opening pages, searching, filling forms, and taking screenshots without re-authentication.
    MIT

  • Alloy MCP

    dragonworx
    F
    license
    Not graded
    quality
    A
    maintenance
    Bonds AI agents to your existing Chrome profile with 73 tools for tabs, DOM, input, screenshots, network, and more, leveraging live sessions and extensions for authenticated, no-setup browser automation.
    -
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.2/5.0

Scored across 17 tools

Disambiguation5/5

Each tool targets a distinct operation: reading page content (read_tab) vs inspecting specific elements (query_dom) vs running custom JS (eval_js), and interaction tools (click, fill, select_option, select_option_ui) have clear boundaries. Even similar tools like scan_matrix/fill_matrix and select_option/select_option_ui are explicitly distinguished by widget type and purpose.

Naming Consistency4/5

Most names follow a verb_noun pattern (list_tabs, read_tab, open_tab, activate_tab, fill_matrix), but a few deviate: navigate, click, fill, and screenshot are single verbs or nouns used as verbs, while browser_status and wait_for use different structures. The pattern is still predictable and readable.

Tool Count4/5

With 17 tools, the set is slightly larger than the ideal 3–15 range but each tool serves a concrete browser automation function (tab management, reading, interaction, waiting, screenshots, matrix handling). The count feels justified for the domain, not bloated.

Completeness4/5

The tool surface covers tab lifecycle (open, close, list, navigate), multiple read modes (markdown, DOM inspection, screenshots), form interaction (fill, click, select, matrix-specific tools), and synchronization (wait_for). Minor gaps exist like no explicit back/forward or keyboard shortcuts, but these can be worked around with navigate or eval_js.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources