Thinking, written down

Everyone asks "MCP or CLI" as if picking a protocol. I tore apart, source by source, the two agent-facing wrappers Feishu built over the *same* OpenAPI — lark-mcp, 1,271 auto-generated atomic tools, and lark-cli, a dozen hand-curated domains. The takeaway isn't which to pick; it's that the question is posed backwards. They're two points on one "coverage × quality" frontier, split apart by who consumes the output. And interestingly, the 20× star gap sends a fairly consistent developer-attention signal — and points to a conclusion that holds for any platform building agent access: the first auto-generated wrapping layer rarely forms a moat.

For a decade, open platforms optimized for how an experienced human would use them. When the caller becomes an Agent, what you measure, what you design, and how you verify all change. Three shifts learned by actually putting an Agent end-to-end on the POIZON Open Platform — plus an unromantic conclusion: the real bar isn't technical.