Skip to main content
Glama
testdino-hq

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to TestDino MCP

No user-submitted related servers found.

    Related Servers

    • Testmo MCP Server

      filipljoljic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Testmo test management platform for creating, reading, updating, and deleting test cases, managing folders, and organizing test runs through natural language.
      4
      MIT

    • TestRail MCP Server

      Derrbal
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with TestRail test management systems through comprehensive API integration. Supports retrieving and updating test cases, projects, suites, runs, and results, plus adding attachments and managing test data through natural language commands.
      18
      32 npm
      MIT

    • TestCollab MCP Server

      TCSoftInc
      A
      license
      A
      quality
      A
      maintenance
      Connects AI coding assistants to TestCollab for managing test cases, plans, and suites directly through natural language. It enables users to create, update, and query testing resources within integrated development environments and AI chat clients.
      20
      45 npm
      4
      MIT
    • Tesults MCP by tesults

      Tesults MCPofficial

      tesults
      A
      license
      Not graded
      quality
      C
      maintenance
      Connect AI agents to your test results, insights, and targets. Query test runs, failures, flaky tests, and regressions across frameworks including Playwright, Jest, Pytest, Cypress and more.
      81 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 58 tools

    Disambiguation3/5

    Many tools target distinct resources, but the debugging and audit areas have several overlapping entry points: get_debug_evidence, debug_testcase, get_flake_verdict, get_trace_analysis, and get_ai_insights all address failing-test diagnosis, with boundaries explained mostly through lengthy cross-references. The audit flow is also split across get_audit_report, submit_audit_report, and show_audit_report. Other areas, such as manual vs. automated tests, are clearer.

    Naming Consistency4/5

    Most names follow a predictable snake_case verb_noun pattern, e.g. create_manual_run, list_releases, update_quarantine. There are minor inconsistencies such as test_case vs. testcase (get_manual_test_case vs. get_testcase_details) and testruns vs. run, plus a few standalone names like health and watch_test. The convention is still readable overall.

    Tool Count1/5

    58 tools is far beyond the well-scoped 3-15 range and falls into the extreme-mismatch threshold of 50+ tools. While the server covers many real subdomains, the surface is too large for an agent to navigate efficiently and increases selection burden.

    Completeness4/5

    Core workflows are well covered: manual cases, suites, runs, sessions, releases, automated-test linking, quarantines, AI insights, debugging, integrations, and audit reports all have lifecycle operations. The main gaps are destructive cleanup operations such as deleting test cases, suites, runs, sessions, or releases, and suite update/delete operations, which agents must currently work around or handle in the UI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources