Skip to main content
Glama
adama007

testlink-mcp-server

by adama007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to testlink-mcp-server

No user-submitted related servers found.

    Related Servers

    • TestRail MCP Server

      denys-ispaniuk
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with TestRail test management system, supporting full CRUD operations on projects, suites, sections, test cases, runs, results, plans, and milestones.
      35
      828 npm
      1
      MIT

    • TestRail MCP Server

      TenBarrel6
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact directly with TestRail instances for managing test projects, suites, cases, runs, results, plans, milestones, and attachments through the TestRail API with secure authentication.
      77
      297 npm
      1
      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
      33 npm
      MIT

    • 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
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.5/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, such as list_projects vs create_project, read_test_case vs get_custom_field_value. Even similar tools like list_test_cases_in_suite and get_test_cases_for_test_plan are clearly differentiated by context (suite vs plan) and description.

    Naming Consistency4/5

    The naming pattern is predominantly verb_noun (list_, create_, update_, delete_, read_, get_). Minor inconsistency between read_ and get_ (e.g., read_test_case vs get_requirement) but the pattern is otherwise predictable and readable.

    Tool Count3/5

    With 30 tools, the server is on the heavier side, but the count is justified by the breadth of the TestLink domain (projects, suites, cases, requirements, plans, builds, executions). Still, it feels slightly over-scoped, especially with several caveat-ridden delete methods.

    Completeness4/5

    The tool set covers the main lifecycle for projects, test suites, test cases, test plans, builds, and executions. Minor gaps exist (e.g., no update_test_plan, no update_requirement, no delete_requirement), but they can be worked around and do not critically hinder core workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources