AsyncAPI Docs Meeting, 16:00 UTC Wednesday May 27th 2026

[asyncapi-bot]

Meeting Info	Details
Purpose	Meeting to triage and coordinate with other maintainers and contributors in the community.
Time	16:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	YouTube Playlist.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Place for your topic
3. Q&A

Notes

Add notes here after the meeting.

[thulieblack]

1. [📑 Docs Discussion]: Epic: Agent-First Documentation & AI Governance Framework #3532
2. feat: add Lychee link checker configuration #3553
3. feat: add Coderabbit config for community documentation #3552
4. [📑 Docs]: An audit across our docs #2294
5. docs: improve contributing docs #3508
6. https://github.com/orgs/asyncapi/discussions/3528#discussioncomment-16881815

Docs Board: AsyncAPI Docs Board (view)
Website Docs Board: Website - Kanban (view)

[thulieblack]

Meeting summary

Quick recap
This meeting focused on reviewing progress and next steps for documentation improvements, with Prince Onyeanuna leading the discussion. The team discussed implementing an MCP server as the primary initiative, with Anton proposing to start with a local Docker image approach before potentially scaling to serverless functions or other hosting solutions. They reviewed progress on link checking tools, where Anton had implemented Lychee as a potential replacement for their current solution and needed help setting up GitHub Actions. The team also addressed issues with the current feedback system, deciding to remove the bot-based anonymous feedback feature due to spam problems and instead direct users to create issues in the website repository with proper attribution. Additional topics included reviewing improved contributing documentation and finalizing text.

Next steps

Mister
Test the Lychee link checker configuration locally and provide feedback to finalize the configuration for CI.
Test the CodeRabbit configuration for link validation and provide feedback.
Offer help to Prince Rajpoot with setting up the epic for user feedback.

Prince Onyeanuna
Research and find YouTube tutorials on how to vectorize functionality and create a database for the MCP server.
Review Christine's PR for improved contributing docs first.

Prince Rajpoot
Help Mister test the Lychee link checker configuration in the CI of a forked repository.
Remove the bot that creates feedback discussions and create an epic in the website repository for user feedback, with a mechanism to create sub-issues.

Thulie
Provide detailed feedback on the CodeRabbit configuration and help Anton test it.

Collaboration
Team: Review the text in the provided PR and give final feedback.

Summary
Epic Discussion Format Conversion Update
The meeting began with technical difficulties as Prince Onyeanuna shared his screen and participants adjusted audio settings. Prince provided an update on a previous discussion about converting an epic into a discussion format to gather more input and reach consensus on Anton's proposed new idea. The team identified that the discussion was still on hold pending additional contributions, with uncertainty about who else should be involved in reviewing the proposal. The conversation ended with Thulie requesting Prince to zoom in the screen before Anton could provide his input.

Local MCP Server Deployment Discussion
Mister proposed starting with a fully local MCP server implementation using a Docker image with a database and LLM for vectorization, allowing users to run it on their local machines. Prince suggested using DigitalOcean for deployment instead of Netlify due to static page deployment constraints, though they need to verify credit and billing details. The discussion focused on finding a suitable hosting solution to avoid requiring users to clone repositories and launch the MCP server manually.

MCP Project Deployment Strategy
Mister and Prince Rajpoot discussed deployment options for their MCP project, focusing on potential limitations with Netlify and serverless functions. Prince Rajpoot confirmed they have Netlify's open source plan, which should not pose a financial issue for deployment. However, Mister expressed concerns about hitting usage limits with serverless functions, particularly when deploying worldwide. As a result, they agreed to start with a local Docker image approach and scale up only if the initial implementation proves useful based on user feedback.

MCP Server Action Plan Discussion
Prince Onyeanuna led a discussion about setting up an action plan for the MCP server to go live, with plans to demo it once ready. Mister suggested Prince start researching YouTube tutorials on vectorizing functionality and creating a database, noting this would be the trickiest part. Thulie asked for clarification on the progress and next steps, which Prince explained involves making documentation more AI-friendly, starting with the MCP server setup.

GitHub Actions Deployment Implementation
Mister reported on his investigation into deployment solutions for Lichi, initially seeking NPM native alternatives but ultimately deciding to proceed with GitHub Actions deployment using Docker containers. He created a draft implementation and needs guidance on adding GitHub actions to their community repository and triggering them properly. Prince confirmed there are no current blockers and suggested making the PR ready for testing locally to gather feedback before implementing it in CI.

Local Configuration Testing Plan
Mister explained the plan to have a final configuration tested locally before deploying it once on CI. Prince Onyeanuna confirmed that the next step is for everyone to test the configuration locally and finalize it before moving to CI. Prince Rajpoot offered to help with testing in the forked repository, and Mister agreed to work with him on this. Mister also discussed a new approach to configure CodeRabbit as a link linter for community documentation, but noted that testing this approach is still pending.

Documentation and Tooling Improvements
The team discussed several documentation and tooling improvements. They decided to remove the bot system for feedback submissions due to spam issues, instead requiring users to create issues manually in the website repository with the docs tag. For the Code Rabbit tool evaluation, Anton and Thulie will work together to test and compare it with Leechee, while Prince and Mason will review Christine's contributing documentation PR. The team also agreed to create an epic for tracking documentation issues and feedback, with Prince Rajpoot taking the lead on implementing this new system.