CometChat docs-MCP: serving a chat SDK's live docs to coding agents (and what actually made the output compile) #810
amitthacker-maker
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Pre-submission Checklist
What would you like to share?
We build a chat / voice / video SDK, and the recurring pain was watching Cursor / Claude / Cline confidently write CometChat integration code against methods that don't exist. Classic "looks right, isn't."
So we shipped a docs MCP — posting it here mostly for one design lesson that surprised us.
What it is
A remote, read-only, no-auth MCP server over our docs:
search_cometchat_docs— search across SDK guides, UI Kit refs, REST API, OpenAPI specsfetch_cometchat_doc_page— full page as markdown by URL/pathget_cometchat_implementation_bundle— a curated recipe for a named scenario (React UI Kit quickstart, Flutter chat + moderation, multi-tenant, presence, …)Endpoint:
https://www.cometchat.com/docs/mcpRepo: https://github.com/cometchat/docs-mcp
The lesson (why I'm posting here, not just linking)
Our first version was only search + fetch. It helped, but the agent still stitched things together wrong — right method names, wrong sequence, missing a required init step. What actually moved the needle
was the implementation bundles: instead of making the model assemble a working integration from doc fragments, we hand it a vetted end-to-end recipe for the exact scenario (prereqs → install → config →
working code → common pitfalls).
Two other things that mattered more than expected:
Net: "let the agent search docs" is table stakes; "hand it a curated bundle for the thing it's building" is what got output that compiled.
Happy to get into how we scoped the tools or the bundle format. Disclosure: it's ours — I work at CometChat.
Relevant Links
All reactions