The second wave of MCP: Building for LLMs, not developers

This post introduces the concept of building 'intention-based' tools for LLMs, contrasting them with 'API-shaped' tools. It argues that LLMs, unlike developers, do not manage state or reuse code across conversations, necessitating tools that encapsulate complete user intentions (workflows) rather than exposing individual API operations. The post provides examples of how this shift improves reliability and efficiency, and suggests designing tools around complete user goals, using regular programming for deterministic parts and involving LLMs only for reasoning or NLP tasks. It also highlights the MCP handler and Next.js MCP template for implementation.