AsyncAPI-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the server listens on | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_asyncapi_spec_versionsA | List stable AsyncAPI specification versions available as GitHub tags. |
| get_asyncapi_spec_metadataA | Return source, version, cache, and size metadata for the latest AsyncAPI specification. |
| search_asyncapi_specA | Search the latest AsyncAPI markdown specification and return matching snippets. |
| validate_asyncapi_specB | Validate raw AsyncAPI YAML or JSON content and return validation errors if the spec is invalid. |
| get_asyncapi_spec_sectionA | Return one section from the latest AsyncAPI markdown specification by heading text or slug. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| asyncapi-spec | The latest AsyncAPI markdown specification fetched from the GitHub master branch. |
| asyncapi-spec-1.0.0 | AsyncAPI markdown specification fetched from GitHub tag 1.0.0. |
| asyncapi-spec-1.1.0 | AsyncAPI markdown specification fetched from GitHub tag 1.1.0. |
| asyncapi-spec-1.2.0 | AsyncAPI markdown specification fetched from GitHub tag 1.2.0. |
| asyncapi-spec-2.0.0 | AsyncAPI markdown specification fetched from GitHub tag v2.0.0. |
| asyncapi-spec-2.0.0 | AsyncAPI markdown specification fetched from GitHub tag 2.0.0. |
| asyncapi-spec-2.1.0 | AsyncAPI markdown specification fetched from GitHub tag v2.1.0. |
| asyncapi-spec-2.2.0 | AsyncAPI markdown specification fetched from GitHub tag v2.2.0. |
| asyncapi-spec-2.3.0 | AsyncAPI markdown specification fetched from GitHub tag v2.3.0. |
| asyncapi-spec-2.4.0 | AsyncAPI markdown specification fetched from GitHub tag v2.4.0. |
| asyncapi-spec-2.5.0 | AsyncAPI markdown specification fetched from GitHub tag v2.5.0. |
| asyncapi-spec-2.6.0 | AsyncAPI markdown specification fetched from GitHub tag v2.6.0. |
| asyncapi-spec-3.0.0 | AsyncAPI markdown specification fetched from GitHub tag v3.0.0. |
| asyncapi-spec-3.0.1 | AsyncAPI markdown specification fetched from GitHub tag v3.0.1. |
| asyncapi-spec-3.1.0 | AsyncAPI markdown specification fetched from GitHub tag v3.1.0. |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: metadata retrieval, section access, version listing, search, and validation. No overlap in functionality.
All tools follow a consistent verb_noun pattern with snake_case, such as 'get_asyncapi_spec_metadata' and 'validate_asyncapi_spec', making it predictable.
With 5 tools, the server covers the core operations for an AsyncAPI spec explorer without being too sparse or excessive.
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.