Skip to main content
Glama

Related Servers

Alternatives to @elsm/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools drive the real, already-logged-in Chrome browser over local stdio—snapshotting and reading pages, clicking, typing, managing tabs, capturing screenshots, and inspecting network, console, storage, and cookies—without opening a remote-debugging port. It installs as a Chrome extension plus native-messaging bridge, so agents work in the user's authenticated sessions while passing bot detection.
      1 npm
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control the user's already-open, logged-in browser pages in real time over a local WebSocket channel, without Playwright, Puppeteer, Selenium, or any browser driver. Exposes tools for navigation, semantic page snapshots, clicking, form filling, JavaScript evaluation, screenshots, network monitoring, cookie handling, and tab management via the CDP.
      20
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets local AI agents drive the Chrome browser a user already has open, including signed-in sessions, by listing tabs, reading page text and actionable elements, then clicking, filling, selecting, scrolling, navigating, and capturing viewport screenshots without exporting cookies. Runs as a dependency-free local stdio process over Native Messaging, with per-tab leases, automatic reconnection, and pause/write-action controls.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI coding tools drive the real Chrome browser you already have open, so they can read and act on logged-in pages with real clicks, typing, navigation, screenshots, and network or storage inspection. Everything runs locally over stdio with no remote-debugging port, so nothing leaves your machine.
      1 npm
      ISC
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed, OAuth-gated suite of 38 tools that let web AI assistants like Claude, ChatGPT, and Grok work directly on your local machine — reading and editing files, running whitelisted shell commands, searching, querying SQLite, driving browsers and DevTools, managing background tasks and localhost services, and controlling Git, clipboard, notifications, and Postman. This lets users build, debug, and maintain projects, inspect databases and local APIs, and check on long-running jobs from a browser or phone without granting unrestricted shell access.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed suite of 38 OAuth-gated tools that let web-based AI chat clients read, write, edit, and search local files, run whitelisted shell commands, inspect databases and localhost APIs, drive browsers and DevTools, and manage background tasks, Git, clipboard, notifications, and ports. Local IDEs connect directly over loopback, while remote clients reach the same machine through a secure tunnel.
      MIT

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (read_cookies vs read_storage vs read_indexeddb vs get_target vs list_storage_areas), and descriptions explicitly disambiguate, e.g. read_storage notes 'Cookies are not an area here — use read_cookies.' The main overlap is export_state, which produces a full snapshot of the same storage areas read_storage reads, so an agent could reasonably pick either for 'dump everything.'

    Naming Consistency5/5

    All nine names follow a consistent snake_case verb_noun convention (read_cookies, write_storage, delete_keys, clear_area, export_state, etc.), including the multi-word list_storage_areas and read_indexeddb. No style mixing.

    Tool Count5/5

    Nine tools sit comfortably in the 3-15 sweet spot and each maps to a concrete capability (read/write/delete/clear across storage areas, cookies, IndexedDB, target introspection, export). Nothing feels padded or missing at the count level.

    Completeness4/5

    Storage lifecycle is well covered (read/write/delete/clear/list plus export), but the surface is asymmetric: cookies and IndexedDB are read-only with no write/delete counterparts, likely by design for safety. An agent could still be blocked if it needs to set a cookie or modify an IndexedDB store, though those are arguably out of scope for a read-inspection bridge.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues