Skip to main content
Glama
pokutuna

@pokutuna/mcp-chrome-tabs

by pokutuna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @pokutuna/mcp-chrome-tabs

No user-submitted related servers found.

    Related Servers

    • agent-browser-ga MCP

      CCl333
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with a user's real Chrome browser tabs, executing JavaScript, reading cookies, and making fetch requests within authenticated sessions.
      -

    • page-bridge

      fannis9
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to read and operate the Chrome or Edge tabs you are already using — titles, URLs, text, HTML, screenshots, clicks, typing, scrolling, and tab management — via a browser extension and native messaging, without restarting the browser, switching profiles, or opening a debug port. It exposes these capabilities as 19 MCP tools, with access limited to explicitly shared tabs and hardened by per-tab, origin-bound grants plus domain allow/deny lists.
      1
      MIT

    • ChromeBrowserMCP

      komaksym
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only bridge that lets ChatGPT inspect open Chrome tabs, exposing tools to list, read, and search tabs without accessing sensitive data.
      15 npm
      MIT

    • tabgrant

      SnakeLil
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request and receive user-granted, short-lived access to a single tab in the user's existing Chromium-based browser, then read, highlight, scroll, and navigate within that granted page without exposing other tabs or copying the browser profile.
      Apache 2.0

    • chromectx

      dyingg
      A
      license
      Not graded
      quality
      D
      maintenance
      Search and retrieve content from all open Chrome tabs, and provide them as context for AI tools via MCP.
      3 npm
      4
      MIT

    • byob

      ChenleSchulz89147
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to drive the user's real, already-logged-in Chrome browser locally, so they can read and navigate pages, click, type, fill forms, take screenshots, and inspect cookies, tabs, console, and network traffic without headless browsers or remote-debugging ports.
      1 npm
      ISC
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_tabs enumerates tabs, open_in_new_tab creates a new tab, and read_tab_content extracts content from an existing tab. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (list_tabs, open_in_new_tab, read_tab_content). The naming is predictable and readable, with no deviations in style or convention across the set.

    Tool Count4/5

    Three tools are well-scoped for a browser tabs management server, covering listing, opening, and reading tabs. While slightly minimal, it is reasonable and each tool earns its place, though additional operations like closing tabs might be expected but are not essential.

    Completeness4/5

    The toolset provides core CRUD-like operations for browser tabs: list (read), open (create), and read content. Minor gaps exist, such as no update or delete tools (e.g., close_tab or update_tab), but agents can work around this, and the surface covers the essential workflows for the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources