Skip to main content
Glama
s-hiraoku

browser-keyboard-mcp

by s-hiraoku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to browser-keyboard-mcp

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      xiyiyiru
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.
      7
      1
      GPL 3.0

    • Browser MCP

      CypherPotato
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.
      11 npm
      -

    • monkeysee

      juliocesar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      4 npm
      1
      MIT

    • Local Browser MCP

      getcabal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local control of existing Chrome/Chromium browser tabs through MCP, including tab management, navigation, content reading, screenshots, and page interaction.
      Apache 2.0

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      53 npm
      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.9/5.0

    Scored across 11 tools

    Disambiguation2/5

    The browser lifecycle, screenshot, and click tools are distinct, but sequence_stop and release_all overlap heavily, and key_down, chord, and sequence_start all cover overlapping key input in ways that could cause misselection. browser_close also includes releasing keys, adding another ambiguous release path.

    Naming Consistency4/5

    Most tools follow a predictable resource_action pattern such as browser_open, browser_close, sequence_start, and key_down, and all names are lowercase snake_case. The standalone chord and verb-first release_all are minor deviations from an otherwise consistent scheme.

    Tool Count5/5

    11 tools is well within the ideal range and each major concern—browser lifecycle, inspection, clicking, key input, sequencing, and status—has dedicated coverage. The overlap between some stop/release tools is more of a naming/selection issue than a count issue.

    Completeness4/5

    The tool set covers browser open/close, screenshot, click, key down/up, chords, timed sequences, and status reporting, so the core workflow is supported. A minor gap is the lack of a navigate-after-open tool, but this can be worked around by reopening or is outside the intended keyboard-focused scope.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources