Skip to main content
Glama
304,906 tools. Last updated 2026-07-22 02:01

"Pytest" matching MCP tools:

  • Generate test skeletons for public functions in untested modules. Writes Jest, pytest, or vitest stubs alongside source files.
    MIT
  • Execute vitest test suite with safety constraints, supporting optional test name filter or path restriction, and return results including pass/fail status, exit code, and duration.
    MIT
  • Run smoke tests automatically before commit or deploy. Detects pytest, jest, vitest, or mocha and executes the test suite from project config.
    MIT
  • Execute JavaScript to query Gaffer test and coverage data, analyze project health, debug failures, and identify untested code areas using codemode API functions.
    MIT
  • Lists every memory in a specified project scope, providing the total count and source breakdown. Use to audit the full inventory and verify if specific memories still exist.
    MIT
  • Run 50 lint dimensions across mechanical, shipped, metabolic, and semantic categories to check substrate contract invariants and auto-repair fixable findings during development or release.
    MIT

Matching MCP Servers

  • F
    license
    -
    quality
    D
    maintenance
    An MCP-compliant server that enables the execution of pytest test suites and the storage of results into a QA platform database. It allows AI models to trigger test runs, track execution progress, and retrieve historical test data through specialized tool interfaces.
    Last updated
    1
  • Extract root-cause-analysis for each failed test from the most recent run, including trace steps, screenshots, and video artifacts.
    MIT
  • Launch interactive test recording to transcribe browser actions into runnable test code. Use to build baseline happy-path tests by clicking through complex UI flows.
    MIT
  • Summarize large lint, test, or CI output files locally. Groups errors by file and type, prioritizing the most important, without consuming Claude's context.
    MIT
  • Execute test suites under the QA runner and generate structured reports with exit codes, logs, and flaky detection. Supports optional filter to target specific tests across pytest, Jest, Cypress, Go, and Maestro.
    MIT
  • Re-run only the tests that failed in the previous run, supporting pytest, Jest, Cypress, Go, and Maestro. Faster than a full suite, ideal for iterative bug fixes.
    MIT
  • Navigate codebases with context, call trees, impact analysis, and change history. Replaces multiple round-trips with single-call actions.
    MIT
  • Delegate a scoped coding task to an external AI worker in an isolated git worktree with independent verification.
    MIT
  • Run an agent repeatedly, using evaluator feedback from each attempt to correct outputs until a success threshold is reached or time/budget constraints trigger a halt.
    MIT
  • Convert candidate test case descriptions into test skeleton files (pytest-playwright, Jest, etc.) with optional pre-filled selectors from URL and module analysis.
    MIT
  • Verifies a QA plan by checking each critical point against provided evidence or auto-discovered test results, outputting a pass/incomplete/fail checklist.
    MIT
  • Requests human feedback via web UI for decisions, clarifications, or approvals, blocking until user responds. Use when multiple valid approaches exist or actions have irreversible effects.
    MIT
  • Parse JUnit XML reports to get a structured summary of test results including totals, failures, errors, skipped tests, and execution time.
    MIT
  • Apply a promoted format-evolution suggestion by automatically editing code, running full test suite, and opening a pull request for human review.
    MIT