作为一个社区，我们需要明白MCP并不是必需的。
1. 为你的AI客户端提供一个“curl”封装，验证允许访问的API方法和端点。
2. 告诉你的AI下载网页文档，并使用html2text、grep、head和tail来发现它所需的信息。
说真的，这样做就是有效的。没有必要让每个人都重新发明自己的MCP服务器。也不需要每次都将整个文档放入提示中。只需改进现有的内容：
- 为你的API端点添加OAuth2，并改善文档。
- 对于命令行工具（CLI），无需将整个帮助信息复制粘贴到SKILLS中，只需改进现有的--help。
如果对非AI用户来说，使用和理解变得更容易，那么对AI本身也会更好，不要重复工作。
上述第1点确实需要某种协议，但不需要在某个地方托管的完整MCP服务器。只需一个JSON文件，AI客户端下载后，用户可以选择允许的API方法/端点组（只读、写入、管理员）。这不需要放入提示中，它是在验证HTTP调用。可以放入提示的内容，例如“只允许只读端点”，以给AI一个提示。就这样！
查看原文
1. Give your AI client a wrapper to "curl" that does validation of what API methods and endpoints is allowed to hit<p>2. Tell your AI to download web docs and use html2text + grep + head + tail to discover what it needs.<p>Seriously, it just works. No need for everyone to reinvent its own MCP server. No need to put your whole documentation every time in the prompt. Just improve what you have:<p>- Add OAuth2 to your API endpoints, and improve your docs.<p>- For CLIs, no need to copy paste your whole help into SKILLS, just improve your existing --help.<p>If things get easier to use and understand for non-AI, then it's also better for AI itself, don't duplicate work.<p>Point 1) above definitely needs some kind of protocol, but not a whole MCP server written in a language hosted somewhere. Just a json is enough that an AI client downloads and the user can select which group of method/endpoint is allowed (Read-only, Write, Admin). THIS DOES NOT need to go in the prompt, it's validating the http calls. What can go in prompt is just e.g. at most "Only read-only endpoints are allowed" to give a hint to the AI. That's it!