wirehack

Makes sense. Both are hard problems I agree.

Yes I agree with you. What are the major shortcomings that you can think of right now (especially the ones that we have not solved)?

yes right forgot to mention this.

Thanks! I think our hosted version has an API endpoint satisfy your needs on mobile devices. You can use our API to call any remote MCP server tools directly. https://docs.klavis.ai/api-reference/mcp-server/call-tool.

Regarding SDKs, yes we are planning to add SDKs as well. The Vercel AI SDK is definitely an interesting one. I will take a look.

Hi yes it sounds like Klavis AI meets your requirement. Can you shoot me an email at xiangkaiz@klavis.ai? Happy to chat!

Got it, thank you for sharing this. Yes I have updated the post so that it is more clear that there are two versions. Thank you for the feedback.

Hi yes so if you just use it yourselves locally in Cursor, I think you can definitely just use the official GitHub MCP. But there might be more use cases where people want to connect MCP servers in their AI agents and deploy it in the cloud, then the local GitHub server would not be a fit.

The UX for end user OAuth is the standard GitHub Oauth flow. You will see a webpage saying that an GitHub Oauth App is requesting access to your github and you need to select yes/no.

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.

Yes thank you! the newest MCP spec added the authentication part but it seems that people think it is still not perfect and are doing more modifications to the auth part. E.g. https://github.com/modelcontextprotocol/modelcontextprotocol.... We will also keep an eye on the spec development.

Hi, you are definitely more than welcome to create PRs in our repo to add more MCP servers.

Yes that is correct.

Hi! Thank you for catching this! I have fixed it right away. This is valuable feedback and I really appreciate it. Now the quick start points to the list of readmes and the hosted version is in the second half of the readme with a clear section Hosted Solutions.

The API is for our hosted version. For open source, you can go to https://github.com/Klavis-AI/klavis and check the comprehensive readme. I think we have readme for every MCP server and client and how to set that up.

> Is there a way to run it locally/self-host?

Yes our github page has README for all MCP servers and clients. You can checkout https://github.com/Klavis-AI/klavis.

> Are there discovery endpoints to list the available servers?

Yes. https://docs.klavis.ai/api-reference/mcp-server/get-all-serv.... And we are adding more MCP servers.

> Testing and Eval

Yes it is early access now. If you are interested, shoot me an email at xiangkaiz@klavis.ai and we can talk more.

Curious to learn what you think about this

Btw I want to mention that it is free to use and try our hosted version as well. Thanks!