Skip to main content
Glama
Souvikns

AsyncAPI-MCP

by Souvikns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AsyncAPI-MCP

No user-submitted related servers found.

    Related Servers

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      8 npm
      3
      MIT

    • EasyPeasyMCP

      derberg
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, zero-config MCP server that makes documentation and API specifications instantly accessible to AI models using the llms.txt standard. It enables searching and retrieving full documentation, OpenAPI, and AsyncAPI specs without requiring a complex RAG infrastructure or vector database.
      4 npm
      1
      Apache 2.0

    • AsyncAPI MCP Server

      Adi-204
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for AsyncAPI that enables parsing, validation, linting, conversion, model generation, and template generation from any MCP client using stdio.
      6 npm
      Apache 2.0

    • speclib-mcp

      rang501
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to search, discover, and retrieve technical specifications from a SpecLib instance. It provides tools for full-text search, scope listing, and reading specs as markdown content.
      -
    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.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: metadata retrieval, section access, version listing, search, and validation. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case, such as 'get_asyncapi_spec_metadata' and 'validate_asyncapi_spec', making it predictable.

    Tool Count5/5

    With 5 tools, the server covers the core operations for an AsyncAPI spec explorer without being too sparse or excessive.

    Completeness4/5

    The tool set covers metadata, sections, versions, search, and validation. Minor gap: no direct way to retrieve the entire raw spec, though sections and search can compensate.

    Resources