AsyncAPI-MCP
The AsyncAPI-MCP server gives AI assistants direct access to the AsyncAPI specification, enabling search, exploration, and retrieval of spec content across versions.
List available versions — Retrieve all stable AsyncAPI spec versions available as GitHub tags
Get spec metadata — Fetch source, version, cache, and size metadata for any spec version (defaults to latest)
Search the spec — Search the AsyncAPI specification by keyword, returning matching snippets (up to 20 results)
Get a specific section — Retrieve a section by heading text or slug (e.g.,
"Info Object"or"info-object")Validate spec files — Validate raw AsyncAPI YAML or JSON content and return any errors
Access structured resources — Retrieve the full spec via resource URIs (
asyncapi://spec/latestorasyncapi://spec/{version})
Most tools accept an optional version parameter (e.g., "3.0.0") to target a specific release, defaulting to the latest.
AsyncAPI MCP Server
An MCP (Model Context Protocol) server that gives AI assistants access to the AsyncAPI specification. Search, explore, and retrieve any version of the spec directly from your coding tool.
Features
Search the AsyncAPI specification by keyword
Retrieve specific sections by heading or slug
List all stable spec versions available as GitHub tags
Get metadata about the spec (version, source, cache info, size)
Version-aware — query any released spec version, or default to the latest
Caching — ETag/Last-Modified-based HTTP caching with a 10-minute TTL on tag lookups
Related MCP server: EasyPeasyMCP
Quick Start
Remote (Self-hosted on Render)
The recommended way to use this server is to deploy your own instance on Render — it's free (no credit card required). Add the following to your MCP client configuration:
{
"mcpServers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}See the Configuration section below for client-specific instructions, and the Deployment section for setup steps.
Local (Self-hosted)
Prerequisites
Node.js v20 or later
Install
npm installBuild
npm run buildRun
Streamable HTTP (for local development):
npm run devThe server starts on http://localhost:3000/mcp by default. Set the PORT environment variable to use a different port:
PORT=8080 npm run devStdio (for local MCP clients):
npm run start:stdioAvailable Tools
Tool | Description | Parameters |
| List stable AsyncAPI spec versions available as GitHub tags | None |
| Return source, version, cache, and size metadata for a spec |
|
| Search the spec and return matching snippets |
|
| Validate raw AsyncAPI YAML or JSON content and return validation errors |
|
| Return a section by heading text or slug |
|
Available Resources
Resource | URI | Description |
Latest AsyncAPI Spec |
| The latest AsyncAPI markdown specification from the master branch |
AsyncAPI Spec by Version |
| A specific version of the spec fetched from the matching GitHub release tag |
Configuration for AI Coding Tools
Remote (Render hosted)
Use these configs to connect to your self-hosted Render instance. Make sure you've deployed the server first.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}Cursor
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}VS Code Copilot
Add to .vscode/mcp.json in your project root:
{
"servers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp",
"type": "http"
}
}
}Windsurf
Add to your Windsurf MCP settings:
{
"mcpServers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}Cline
In Cline's MCP settings, add:
{
"mcpServers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}OpenCode
Add to your OpenCode configuration:
{
"mcp": {
"servers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}
}Zed
Add to your Zed settings.json:
{
"context_servers": {
"asyncapi": {
"url": "https://asyncapi-mcp.onrender.com/mcp"
}
}
}Local (Self-hosted)
Use these configs when running the server locally with npm run dev. Make sure the server is running before connecting.
Claude Desktop
{
"mcpServers": {
"asyncapi": {
"url": "http://localhost:3000/mcp"
}
}
}Cursor
{
"mcpServers": {
"asyncapi": {
"url": "http://localhost:3000/mcp"
}
}
}VS Code Copilot
{
"servers": {
"asyncapi": {
"url": "http://localhost:3000/mcp",
"type": "http"
}
}
}Windsurf / Cline / OpenCode / Zed
Replace the Render URL in the configs above with http://localhost:3000/mcp.
Deployment
Render (Recommended — Free, easy setup)
Render provides a free web service tier with no credit card required. This is the easiest way to host your MCP server.
Free tier behavior
750 free instance hours per month — plenty for a single MCP server
Sleeps after 15 minutes of idle time — the service spins down when nobody is using it
Wakes up on next request — takes about 30–60 seconds to respond after sleep
No credit card required — truly $0
Prerequisites
Your code pushed to a public GitHub repository
Deploy via Git
In the Render dashboard, click New → Web Service.
Connect your GitHub account and select your repository.
Render will auto-detect the Node.js buildpack.
Set the following:
Name:
asyncapi-mcp(or whatever you prefer)Runtime:
NodeBuild Command:
npm install && npm run buildStart Command:
npm startInstance Type:
Free
Add environment variable:
PORT=3000
Click Create Web Service.
Render will build and deploy your app. Once finished, you'll get a public URL like https://asyncapi-mcp.onrender.com.
Configure your MCP client
Your Render domain is already configured in the Configuration section above.
Health check
You can verify the server is running by visiting:
https://asyncapi-mcp.onrender.com/healthSelf-hosted (Docker)
Build and run with the included Dockerfile:
docker build -t asyncapi-mcp .
docker run -p 3000:3000 asyncapi-mcpThe HTTP server will be available at http://localhost:3000/mcp.
Self-hosted (Local machine)
npm install
npm run build
npm startThe server starts on http://localhost:3000/mcp by default.
Usage Examples
Once configured, you can ask your AI assistant questions like:
"What does the AsyncAPI spec say about server objects?"
"Search the AsyncAPI spec for 'channels'"
"Get the Info Object section from version 2.6.0"
"List all available AsyncAPI spec versions"
"What are the differences between messages in AsyncAPI 2.x and 3.x?"
"Show me the spec section about schema definitions"
Development
# Install dependencies
npm install
# Build TypeScript to dist/
npm run build
# Run the HTTP server (local development)
npm run dev
# Run the stdio server (for local MCP clients)
npm run start:stdio
# Type-check without emitting
npx tsc --noEmitMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceAn 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.Last updated
- Alicense-qualityCmaintenanceA 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.Last updated361Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.Last updated72310MIT
- Alicense-qualityBmaintenanceAn MCP server for AsyncAPI that enables parsing, validation, linting, conversion, model generation, and template generation from any MCP client using stdio.Last updated31Apache 2.0
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Souvikns/asyncapi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server