Skip to main content
Glama
kirti676

API Tester MCP

by kirti676
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to API Tester MCP

No user-submitted related servers found.

    Related Servers

    • qa-mcp

      davidpoza
      A
      license
      C
      quality
      C
      maintenance
      Automates generation of QA artifacts such as API tests, E2E tests, and documentation exports. It supports REST Assured, Cypress, and Excel/Word document generation.
      5
      9 npm
      MIT

    • API Testing MCP

      amyzlp
      F
      license
      Not graded
      quality
      C
      maintenance
      A full-stack API automation testing server that parses OpenAPI/Swagger/Postman/HAR specs, generates comprehensive test scenarios and executable code, and provides AI-powered review and auto-fix.
      -

    • agentic-api-testing

      rangarajan19
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language chat-driven API testing, letting users upload API specs, run deterministic pytest checks against live targets, inspect results, create defects, and view failure trends.
      MIT

    • qa-ai-agents

      abchahal
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables automated QA testing by running a pipeline of AI agents that generate test scenarios, architect test layers, write Playwright tests, and review code, all grounded in feature requirements and API contracts.
      -

    • heimdall

      AntreasAntoniou
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to author, validate, and execute browser/API test plans with parallel drivers, assertions, and captured evidence such as screenshots and network logs.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes, but debug_file_system and get_workspace_info both provide workspace information, which could cause minor confusion. The descriptions help differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., generate_scenarios, run_api_tests). No mixed conventions or ambiguous verbs.

    Tool Count5/5

    11 tools is appropriate for an API testing server. Each tool serves a clear purpose in the workflow without being excessive or insufficient.

    Completeness4/5

    The tool set covers the core API testing workflow: ingestion, setup, scenario/test generation, execution, and diagnostics. Minor gaps include inability to view generated content directly or delete resources, but these are not critical.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources