Skip to main content
Glama

Related Servers

Alternatives to tarn-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.
      10
      57 npm
      1,750 PyPI
      137
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local, MIT-licensed AI test harness with 10 MCP tools and 11 prompts for risk-based testing, accessibility checks, quality maps, evidence, and interactive reports. Runs over stdio against an explicitly configured project folder; uses the host AI coding agent, with no hosted backend or runtime telemetry.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      mcp-test-runner is an MCP server that lets your AI client (Claude / Cursor / Codex / Gemini) drive your entire QA loop end-to-end: * Run tests across pytest / Jest / Cypress / Go / Maestro — single MCP surface, one env var to switch * Analyze a URL (Web DOM probe) or a live mobile screen (Maestro hierarchy) to extract testable modules + candidate cases * Generate runna
      22
      54 PyPI
      37
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language testing of MCP servers—covering tools, resources, prompts, contracts, and transports—without writing test code, with deterministic validation and CI integration.
      63 npm
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Tools are largely distinct, but tarn_run and tarn_run_agent overlap in purpose despite differing modes, and tarn_last_failures/tarn_last_root_causes/tarn_report have subtle granularity differences that could cause minor confusion.

    Naming Consistency5/5

    All tools follow a consistent tarn_verb_noun or tarn_noun pattern in snake_case, making the set predictable and easy to navigate.

    Tool Count5/5

    14 tools cover the full lifecycle of testing with Tarn without being excessive; each tool serves a clear, non-redundant role.

    Completeness5/5

    The tool surface includes running tests, inspecting results in multiple granularities, impact analysis, scaffolding, validation, and fix planning—leaving no obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessSlow