Skip to main content
Glama
vschernoff

forge-test-mcp

by vschernoff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to forge-test-mcp

No user-submitted related servers found.

    Related Servers

    • playwright-e2e-mcp

      trajectiq-ai
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to run, debug, and inspect Playwright end-to-end tests, returning structured pass/fail stats, failure diagnostics with actionable fix hints, live DOM inspection, selector validation, visual diffs, and flakiness verdicts instead of raw test output.
      11
      0
      MIT

    • ToolchainConductor MCP

      johannschiffer
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to discover installed host compilers, execute builds in isolated child environments with timeout enforcement, and convert noisy ANSI-laden compiler logs from Python, Rust, C/C++, Node, and Go toolchains into clean structured JSON diagnostics. It also reports toolchain readiness so agents can avoid blind invocations of missing compilers.
      4
      MIT

    • verdict

      Dgotlieb
      A
      license
      A
      quality
      B
      maintenance
      Provides structured, sandboxed test and lint feedback for coding agents, returning compact typed verdicts with failure fingerprints instead of raw runner output. It enables impact-selected test execution in isolated containers, distinguishing pre-existing failures from regressions.
      4
      27 PyPI
      Apache 2.0

    • Build MCP Server

      TeodorTrotea
      A
      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
      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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    run_tests, explain_failure, and build have clearly distinct purposes: one runs the suite, one drills into a single failure at high verbosity, one compiles. An agent can easily route each request.

    Naming Consistency4/5

    run_tests and explain_failure follow verb_noun, while build is a bare verb. Minor deviation but still readable and predictable.

    Tool Count4/5

    Three tools is slightly thin but each earns its place covering the core workflow of build, run, and diagnose. Well-scoped for a focused Foundry testing server.

    Completeness4/5

    The build-run-explain lifecycle is fully covered, including structured compiler output and fuzz/invariant counterexamples. Minor gaps like listing tests or coverage exist but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources