Skip to main content
Glama
Sign In
BoomBidiBuyBuy

tuskr-mcp-server

by BoomBidiBuyBuy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tuskr-mcp-server

No user-submitted related servers found.

    Related Servers

    • tuskr-mcp

      Zapkid
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Tuskr test management that allows browsing, searching, reading, creating, and updating test cases, suites, sections, and test runs from any MCP host like Cursor.
      17
      MIT

    • mcp-kiwi-tcms

      runitsolutions
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Kiwi TCMS test management system through MCP, supporting read and write operations on test plans, cases, runs, and executions, with API key authentication.
      1
      AGPL 3.0

    • rtm-mcp

      ngocdd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients to directly manage Jira Requirements and Test Management resources such as requirements, test cases, plans, executions, defects, tree structures, and automation via exposed tools.
      10 npm
      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.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct operations across test runs, test cases, results, suites, and projects. The main overlap is add_test_case vs upsert_test_case and the several run-reading tools, but the detailed descriptions explicitly differentiate them, reducing misselection risk.

    Naming Consistency5/5

    All tool names use snake_case with a predictable verb_noun structure such as create_test_run, get_test_run_results, and list_test_cases. Minor compound verbs like bulk_export are still readable and consistent with the overall convention.

    Tool Count4/5

    Sixteen tools is slightly above the ideal compact range but justified by the breadth of the test-management domain: runs, cases, results, suites, projects, export, archiving, and locking. Each tool maps to a reasonably distinct operation rather than redundant surface area.

    Completeness3/5

    The core lifecycle for test runs, test cases, and results is covered, including creation, listing, result recording, locking, archiving, and export. However, there are notable gaps: no dedicated suite/section management beyond listing, no project creation/update, no test run metadata editing, and no restore-from-archive operation.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources