Skip to main content
Glama
rscoelho

@clikta/mcp-server

by rscoelho

Related Servers

Alternatives to @clikta/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code drive your own Chrome browser with human-like clicks, drags, and typing. It uses your real sessions and logins, and pauses for your confirmation on anything irreversible.
      8
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to directly control a persistent, real logged-in Chrome browser via 17 browser tools and 9 trading tools, with natural-language selectors, self-healing element resolution, and risk-limited trading operations.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.
      -
    • F
      license
      A
      quality
      C
      maintenance
      Gives Claude control of a real, headed Chromium browser via Playwright, enabling web navigation, clicking, typing, screenshots, and JavaScript evaluation.
      8
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language browser automation through Claude, wrapping Playwright to execute commands like navigation, clicking, form filling, and screenshots.
      5 npm
      30
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: navigation, recording control, interaction (click/type), annotation (note), capture (screenshot), and listing queries. There is no overlap or ambiguity between tool roles.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern, with verbs like start, finish, click, type, list, and screenshot. The clikta_ prefix unifies the namespace, and naming is predictable across the entire set.

    Tool Count5/5

    With 9 tools, the server is well-scoped for its purpose—recording browser sessions and generating guides. Each tool fills a necessary role in the workflow, with no clutter or redundancy.

    Completeness4/5

    The tool set covers the full lifecycle of creating a recording: start, navigate, interact, annotate, screenshot, and finish with publishing. Minor gaps exist, such as no update/delete for recordings, but these are not core to the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues