Skip to main content
Glama
maderwin

pinchtab-mcp

by maderwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to pinchtab-mcp

No user-submitted related servers found.

    Related Servers

    • cdpilot

      mehmetnadir
      A
      license
      Not graded
      quality
      A
      maintenance
      Zero-dependency browser automation CLI with 40+ commands. Navigate, click, fill forms, take screenshots, capture network traffic, and more — all via Chrome DevTools Protocol. Built-in accessibility tree snapshots for AI agents (500x fewer tokens than screenshot-based approaches). Works with any Chromium browser already installed. 50KB total, no Playwright or Puppeteer needed.
      21 npm
      30
      MIT

    • Playwright MCP

      Playwright-os
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables browser automation through Playwright using accessibility tree snapshots instead of screenshots. Supports web scraping, form interactions, testing, and connecting to existing browser sessions with logged-in accounts.
      22
      23
      4,799 npm
      5
      -

    • veilbrowser

      acunningham-ship-it
      A
      license
      A
      quality
      A
      maintenance
      Stealth browser automation over raw CDP, driving a real unmodified Chrome with no Playwright or Puppeteer in the stack. Returns numbered element refs from the accessibility tree so a model clicks ref 3 instead of guessing a CSS selector, and can attach to an already-running Chrome to reuse logged-in sessions.
      33
      76 npm
      41
      MIT

    • Web Bridge

      JohnXu22786
      A
      license
      A
      quality
      B
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      30 npm
      MIT

    • OpenBrowser

      dylansantwani
      A
      license
      Not graded
      quality
      A
      maintenance
      A zero-dependency MCP server that drives a real Chrome browser through a companion extension, enabling AI agents to automate real user sessions with trusted input events, compact accessibility-tree snapshots, and 14 tools for navigation, interaction, scripting, and inspection.
      302 npm
      1
      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

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct browser automation action (click, type, scroll, navigate, etc.) with no functional overlap. Even similar actions like click vs focus vs hover are clearly differentiated by their descriptions and use cases.

    Naming Consistency4/5

    All tools use the pinchtab_ prefix and snake_case. However, there is a minor inconsistency: some tools use verb_noun (e.g., pinchtab_list_instances, pinchtab_get_text) while others are just a noun (e.g., pinchtab_cookies, pinchtab_screenshot) instead of pinchtab_get_cookies or pinchtab_take_screenshot.

    Tool Count5/5

    19 tools cover the essential browser automation operations without being excessive. Each tool serves a clear purpose, and the number feels well-scoped for a comprehensive automation server.

    Completeness4/5

    The tool set covers most common browser interactions: navigation, input, events, screenshots, PDF, cookies, evaluation, and tab management. Missing features like file upload or drag-and-drop are minor gaps that can be worked around with eval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources