Skip to main content
Glama
cocaxcode

API Testing MCP

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to API Testing MCP

No user-submitted related servers found.

    Related Servers

    • bruno-mcp

      jackmulligan-ire
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that executes requests from Bruno API collections via the Bruno CLI tool, enabling API request execution and collection management.
      4
      MIT

    • bruno-mcp

      gpact
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server that lets clients discover, inspect, and execute Bruno OpenCollection API collections, while delegating request execution, authentication, scripting, assertions, and environment resolution to the Bruno CLI.
      11
      176 npm
      1
      MIT

    • Postman MCP Generator

      harichandra599
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that converts Postman API requests into executable tools for LLMs using the Postman Runtime. It supports complex authentication types and enables seamless integration between Postman collections and MCP clients like Claude Desktop.
      -

    • Postmancer

      hijaz
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for API testing and management, allowing AI assistants to interact with RESTful APIs through natural language.
      12 npm
      28
      MIT

    • mcp-server

      gwanghun-choi
      A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1
    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

    A3.6/5.0

    Scored across 42 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, covering areas like API spec management, environment handling, request execution, testing, and collections. Descriptions are detailed and specific, leaving no ambiguity about what each tool does.

    Naming Consistency5/5

    All tool names use snake_case consistently, following verb_noun or noun_verb patterns. The naming is predictable and readable, despite the large number of tools.

    Tool Count2/5

    With 42 tools, the server exceeds the recommended range for a well-scoped MCP server. While the domain is broad, the high count may overwhelm agents and suggests potential for consolidation or modularization.

    Completeness5/5

    The tool set covers the full lifecycle of API testing: importing specs, managing environments, executing requests, running tests, and exporting collections. There are no obvious gaps, and the tools support complex workflows like flows and load testing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources