Skip to main content
Glama
josvaal

yatt-ts

by josvaal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to yatt-ts

No user-submitted related servers found.

    Related Servers

    • Playwright Automation MCP

      devqa07
      F
      license
      A
      quality
      D
      maintenance
      Enables AI-powered browser automation controlled through natural language, integrating Playwright with the Model Context Protocol to perform web interactions like navigation, form filling, and screenshots.
      10
      -

    • Playwright MCP with Electron

      robertn702
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables Model Context Protocol tools for automating web browsers and Electron desktop applications using Playwright's accessibility tree snapshots. It supports window management and JavaScript execution in the main process, providing deterministic automation through structured data.
      241 npm
      17
      Apache 2.0

    • MCP Playwright Server

      j0hanz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control web browsers through Playwright automation, providing 50+ tools for navigation, interaction, testing, accessibility audits, and visual testing across Chromium, Firefox, and WebKit.
      6 npm
      MIT

    • Playwright MCP Server

      devskido
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.
      32
      15,344 npm
      MIT

    • AIAgentMCP

      pavanmareddy-git
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables browser automation and testing using Playwright through the Model Context Protocol.
      -
    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

    B3.4/5.0

    Scored across 35 tools

    Disambiguation4/5

    The tool set is organized by clear resource prefixes (test_, report_, browser_, tab_, session_), and each operation targets a distinct resource or action. A few browser-related tools such as browser_run_step, browser_condition, and browser_click_at have overlapping interaction/inspection responsibilities, but the descriptions clarify their boundaries.

    Naming Consistency4/5

    The vast majority of tools follow a consistent snake_case verb_noun pattern, e.g. test_create, browser_open, and session_delete. The exceptions are ping and schema, which are single-word names that do not follow the pattern but are still clear and unlikely to confuse.

    Tool Count2/5

    35 tools is well over the 25+ threshold and creates a heavy selection surface for an agent. The tools are logically grouped, but the overall count feels excessive for a single MCP server even though each tool has a legitimate role in the testing workflow.

    Completeness4/5

    The test lifecycle is well covered: create, read, update, delete, rename, duplicate, validate, run, and export are all present. Minor gaps exist in baseline management, which only offers list and get with no create/delete, and reports lack comparison or export operations, but these are workable gaps.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources