Hi everyone, Bumping this thread for visibility. If anyone has feedback or would like to discuss KIP-1318, please let me know.
Otherwise, if there no questions or concerns, I will proceed with calling a vote in the next few days. Thanks, Vaquar Khan On Thu, May 14, 2026, 9:17 PM vaquar khan <[email protected]> wrote: > HI Manan, > Thank you for your support! I am glad you find the idea of a native MCP > server for Kafka useful. You are absolutely welcome to contribute > collaboration and PRs are highly appreciated as we move forward with this > feature. Let's sync up on the Jira ticket (KAFKA-20436) regarding specific > areas you'd like to tackle. > > > To the wider community: > Please let me know if you have any further questions, feedback, or > concerns regarding KIP-1318. > > I would love to discuss any thoughts or architectural suggestions you > might have. > If there are no major issues or objections raised during this discussion > period, I plan to bring this KIP forward for a formal vote soon. > > Looking forward to hearing from you all. > > Regards, > Viquar Khan > LinkedIn - https://www.linkedin.com/in/vaquar-khan-b695577/ > > > On Thu, May 7, 2026, 2:01 PM Manan Gupta <[email protected]> wrote: > >> Hey Vaquar >> >> Thank you for the KIP. >> I like the idea of creating an MCP server for Kafka. >> I think it will be quite useful. >> Can I contribute some changes for this feature? >> >> Regards, >> Manan Gupta >> >> On Wed, Apr 22, 2026 at 8:56 AM vaquar khan <[email protected]> >> wrote: >> >> > Hi everyone, >> > >> > I would like to start a discussion on *KIP-1318: Model Context Protocol >> > (MCP) Server for Apache Kafka*. >> > >> > *KIP Interface:* KIP-1318 Wiki >> > < >> > >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1318%3A+Model+Context+Protocol+%28MCP%29+Server+for+Apache+Kafka >> > > >> > *JIRA:* KAFKA-20436 <https://issues.apache.org/jira/browse/KAFKA-20436 >> > >> > >> > *Motivation*: >> > >> > Currently, interacting with Apache Kafka programmatically requires >> writing >> > Java/Python code, using CLI tools, or relying on Connect REST APIs none >> of >> > which are natively accessible to autonomous AI agents via the Model >> Context >> > Protocol (MCP). >> > >> > While some community-led MCP implementations for Kafka exist, they often >> > lack critical enterprise capabilities like ACL management and >> transactional >> > operations, or they are tightly coupled to specific vendor platforms. >> This >> > KIP proposes adding a first-party, Apache-licensed MCP server to the >> Kafka >> > project. >> > Key Highlights >> > >> > - >> > >> > *New Standalone Module:* Introduces tools/mcp-server, a JSON-RPC 2.0 >> > server that runs outside the broker process. >> > - >> > >> > *Zero Protocol Changes:* This proposal requires no changes to the >> Kafka >> > wire protocol or existing public APIs. It acts as a wrapper around >> > native >> > Java client APIs. >> > - >> > >> > *AI-Native Operations:* Allows AI agents to manage topics, handle >> > consumer groups, and read/write messages using a standardized >> interface. >> > - >> > >> > *Security First:* It will pass through all standard Kafka security >> > properties (SASL, SSL, ACLs) directly to the underlying clients. >> > >> > I look forward to your feedback and suggestions. >> > >> > >> > Regards, >> > Vaquar Khan >> > *Linkedin *-https://www.linkedin.com/in/vaquar-khan-b695577/ >> > >> >
