Praveenkumar76 commented on issue #25881: URL: https://github.com/apache/pulsar/issues/25881#issuecomment-4611821980
Hi @Chinakeyboardman , I'd help out with this and pick up the Phase 1 implementation (the official Pulsar MCP Server) Regarding the alternative suggestion from @Denovo1998 about encapsulate this via the `pulsar-admin` CLI, while that's a quick way to give an LLM access, I believe building a native MCP server translating to the REST API is the stronger architectural choice for a few reasons like: 1. **Structured Data vs. Unstructured Text:** The REST API returns clean JSON, which is much more reliable for an agent's context window. Parsing raw CLI stdout text often leads to LLM hallucinations or parsing errors. 2. **Zero Dependencies:** An MCP Server can be distributed as a standalone binary or Python package. If we rely on the CLI, any developer wanting their agent to interact with Pulsar must also install Java and the Pulsar client binaries on the agent's host machine. 3. **Ecosystem Alignment:** MCP is rapidly becoming the standard for direct agent-to-infrastructure communication (as seen with Doris and Postgres). A native MCP implementation makes Pulsar instantly discoverable in tools like Cursor and Claude Desktop without complex environment setups. If the community is aligned on this direction, I can start building a lightweight Proof of Concept (PoC) for the `pulsar-mcp-server` in Python or Go, covering just the basic Topic Admin and Observability tools. Let me know if you are open to a PoC PR for Phase 1! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
