构建智能体同时考虑消费者需求

Good take. Build for agents, but also keep in mind that you have consumers with different needs, dem...

Good take. Build for agents, but also keep in mind that you have consumers with different needs, demanding different experiences. MCP/CLIs, where it stands today, cannot possibly cover all these needs. BTW, check out WebMCP to build richer agentic, human-centered experiences. So much alpha to uncover. Ashpreet Bedi @ashpreetbedi There is a popular twitterpinion going around that companies should stop building agents and only expose MCPs/CLIs. I agree the old way of clicking through a UI is going away but this take is short sighted and misses nuance. It is almost impossible to expose the full strength of a product through a flat list of tool calls. The API calls behind a real workflow need careful orchestration. And authz is incredibly hard in a headless interface. Companies that want to take advantage of this shift need all three: 1. An MCP their users can plug into any agent 2. An in-product agent: a carefully curated experience the company controls, owns, and learns from. It becomes a new way of using the product. 3. The product agent exposed through the MCP. Users get the company's agent through their agent of choice. Simple requests like "pull up my subscriptions on stripe" go through the MCP tools. Complex, curated experiences go through the company's agent (accessed via MCP as well). Everything should be reachable through MCP, so your agent can talk to my agent. But expecting a general-purpose agent to orchestrate a complex chain of tool calls in the right order every time, is laughable. The orchestration is the product. The problem is that most companies haven't cracked that yet... so its easy to say: give me all the tools. That's like saying let me use your REST API directly. We just haven't seen the good agentic experiences yet and making this take the standard means we never will. 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 2 👀 690 📊 1 ⚡