Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does this mean that we'd have to store our various keys/credentials with you (in the hosted solution).

If so, I would emphasize or add more documentation on how you are securing credentials.

And how would I add this to my agent? Would you have One MCP To Rule Them All?



Yes thank you for the good feedback. We will update our doc to reflect this.

> how would I add this to my agent? Would you have One MCP To Rule Them All?

If you are talking about the hosted version, you can go to our website to grab an API key and call the corresponding endpoint. https://docs.klavis.ai/documentation/mcp-server/github is the doc for GitHub MCP server.

in terms of one mcp to rule them all, it is something on our roadmap now. We are thinking that you can connect to all of the MCP servers we provide with a single URL and you can turn on/off the MCP servers in a simple UI or through API call. Let me know if this is what you have in mind.


Right now, as you know we’re in a total Wild West with this. So the experience is different for each client (VS code, cursor, etc)

To me, the ideal the UX is similar to the extensions UXs in each IDE, you search, click install, and get on with your life after doing an OAuth dance. Or even a discovery mechanism built into the agent itself. Sort of a “have you considered installing this? I can talk directly to JIRA for you” etc

The next best thing would be a catalog where I search, and with a single install button that would add the MCP to a certain IDE. But do the IDEs make this sort of API available, given that they all want to differentiate?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: