Skip to main content
Glama
simplypixi

BugBug MCP Server

by simplypixi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to BugBug MCP Server

No user-submitted related servers found.

    Related Servers

    • Build MCP Server

      TeodorTrotea
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage development workflows by running build commands, executing tests, analyzing package.json files, installing dependencies, and performing code linting. Supports multiple package managers (npm, yarn, pnpm) and provides detailed error reporting for development operations.
      5
      -

    • Godot Sentinel MCP

      AustinMander
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Godot game projects through real-time error detection, automated testing, code analysis, and safe git-based patching. Provides comprehensive project context and development workflow automation for Godot developers.
      MIT

    • GitHub MCP Server

      asbloom-py
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with GitHub through the GitHub API, supporting file operations, repository management, advanced search, and issue tracking with comprehensive error handling and automatic branch creation.
      358 npm
      1
      ISC

    • LoadRunner Cloud MCP Server

      pbandreddy
      F
      license
      B
      quality
      D
      maintenance
      Enables automated access to LoadRunner Cloud APIs for retrieving performance test data, managing projects, and collecting test results. Supports integration with AI clients for building performance engineering workflows and dashboards.
      9
      -
    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.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources (IP addresses, profiles, suites, tests, runs) and actions (get, run, stop, wait). However, some overlap exists between 'get_suite_run' and 'wait_for_suite_run' (both return suite run data) and between 'get_test_run' and 'wait_for_test_run', which could cause confusion about when to use each.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, primarily using 'get_' for retrieval, 'run_' for execution, 'stop_' for termination, and 'wait_' for monitoring. The only minor deviation is 'show_run_from_last_24', but it still fits the verb_noun convention and is readable.

    Tool Count3/5

    With 20 tools, the count is borderline high for a test automation server, feeling slightly heavy. While the tools cover various aspects (profiles, suites, tests, runs, screenshots, status), some could potentially be consolidated (e.g., multiple 'get_' tools for similar resources).

    Completeness5/5

    The tool set provides comprehensive coverage for the BugBug test automation domain, including CRUD-like operations (get lists and details), execution (run, stop), monitoring (wait, status), and auxiliary functions (screenshots, IP addresses). There are no obvious gaps; agents can manage the full lifecycle of tests and suites.

    Resources