Skip to main content
Glama
Mhdd-24

@mhdd_24/api-scenario-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @mhdd_24/api-scenario-mcp

No user-submitted related servers found.

    Related Servers

    • api-testing-agent

      SHREELASYABEZAWADA
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.
      1
      -

    • TalkAPI

      prakhar7824
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables conversational API testing via MCP, allowing users to make HTTP requests, decode JWT tokens, and validate JSON schemas through natural language.
      -

    • Any-API MCP Server

      ghively
      A
      license
      B
      quality
      B
      maintenance
      A configurable MCP server that adapts any HTTP API into an MCP toolset with generic HTTP tools (GET, POST, PUT, DELETE) and pluggable authentication. Includes API discovery scripts and supports dynamic tool generation from OpenAPI specs or wordlist scans.
      5
      1
      MIT

    • ControlAPI-MCP

      fellowabhi
      A
      license
      A
      quality
      C
      maintenance
      Converts any OpenAPI/REST API into MCP tools with dynamic server switching, variable substitution, and runtime configuration. Enables seamless interaction with multiple API environments through natural language without pre-configuration.
      12
      5
      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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: status is a health check, generate creates a workflow, and to_http converts an outline to HTTP steps. There is no meaningful overlap or ambiguity among the three tools.

    Naming Consistency4/5

    All tools share the consistent apiscen_ prefix and use snake_case, but the naming pattern is slightly uneven: status is a noun, generate is a verb, and to_http is a converter-style phrase. The naming is still predictable and readable overall.

    Tool Count5/5

    Three tools is an appropriate size for this focused API scenario utility. Each tool supports a distinct part of the workflow without being redundant or bloated.

    Completeness4/5

    The core pipeline of generating a scenario and converting it to HTTP steps is covered, with a health check for operational use. Minor gaps exist, such as no explicit validation or management tools for scenarios, but they do not undermine the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources