Skip to main content
Glama

Related Servers

Alternatives to Cortex Browser MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Token-optimized Playwright MCP server that reduces context window usage by 73.8% by grouping 22 tools into 6 semantic operations, enabling AI assistants to control browsers with minimal token overhead.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control, read, and verify a live Chrome browser through 46 schema-validated MCP tools, including DOM pruning, coordinate-aware interaction, and trusted CDP input events.
      77 npm
      41
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to drive a Chromium browser through MCP, with persistent sessions, compact page snapshots, guarded actions, batched operations, and explicit result verification.
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to control a visible Chromium browser via Playwright with tools for tabs, page reading, element finding, form input, mouse/keyboard actions, screenshots, console/network inspection, JavaScript execution, viewport emulation, and batched calls.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to automate a real Chromium browser through the unchanged upstream Playwright MCP tool surface, covering navigation, research, testing, and daily web workflows in plain language. It ships via npm or Docker over stdio or Streamable HTTP, and supports persistent login profiles, Chrome extension loading, proxy/GeoIP matching, and humanized mouse, keyboard, and scroll behavior.
      280 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools map to distinct phases: open navigates, peek reads/extracts, run performs actions/asserts, and debug diagnoses. However, peek and run both support extraction, so an agent could reasonably hesitate between them when the task is only to extract data.

    Naming Consistency5/5

    All tools use the same cortex_ prefix followed by a short lowercase verb. The pattern is fully predictable across open, peek, run, and debug.

    Tool Count5/5

    Four tools is lean but appropriate for a focused browser automation server. Each tool covers a distinct interaction phase and none appears redundant.

    Completeness4/5

    The set covers the core browser loop: navigation, inspection/extraction, actions/assertions, and diagnostics. Minor gaps exist around explicit session close/history or standalone screenshot control, but they are workable through the provided tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues