Skip to main content
Glama
Naveen-Automation

api-testing-mcp

by Naveen-Automation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to api-testing-mcp

No user-submitted related servers found.

    Related Servers

    • AIAgentMCP

      pavanmareddy-git
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables browser automation and testing using Playwright through the Model Context Protocol.
      -

    • mcp-playwright

      executeautomation
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      32
      7,948 npm
      5,644
      MIT

    • Playwright MCP

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.
      4,633,135 npm
      Apache 2.0

    • Playwright MCP Server

      devskido
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.
      32
      7,948 npm
      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

    C2.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool corresponds to a distinct HTTP method (DELETE, GET, POST, PUT) with no overlap, making it trivial for an agent to select the correct one.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'send-{method}-request' with lowercase and hyphens, ensuring predictability.

    Tool Count5/5

    With 4 tools covering the main HTTP methods (CRUD), the count is well-suited for an API testing server—neither too few nor too many.

    Completeness4/5

    The set covers the most common HTTP methods, but omits PATCH and other less common ones. For basic testing, it is sufficiently complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources