What did Meta announce? On September 15, Meta opened WhatsApp Business setup to third-party AI agents. Through a new WhatsApp Business Tools MCP server, a coding agent — Claude, Cursor, Codex, ChatGPT — can now create a WhatsApp Business account, verify its phone number, register it for the Cloud API, and check the business Terms of Service. Agents can also write and edit message templates, test webhooks, and monitor the quiet failure points (ToS status, payment method, business verification) that used to silently break integrations.

Why is this more than a feature? Because of the mechanism: MCP — the Model Context Protocol. Setup used to mean juggling the Developer Console, Business Manager, the API reference, and your editor. Now it's a conversation with your agent. Meta is one of at least a dozen majors (PayPal, Stripe, GitHub, Notion, Slack, Salesforce, Atlassian, X, Google, Microsoft) shipping MCP servers. That's not a feature race — it's a protocol land-grab. Whichever protocol agents speak becomes the USB-C of the agent era.

What's the pattern to watch? Agents are graduating from assistants to operators. The first jobs they take aren't the clever ones — they're the procedural busywork nobody enjoys: account creation, verification, template plumbing. That's deliberate. The boring parts are where reliability gets proven.

The personal angle (lscppdev voice): Recently I co-directed a soda ad with my agent, Bob. This week Meta handed agents the keys to business onboarding infrastructure. The gap between "my agent helped me make a thing" and "my agent runs the plumbing" is closing fast — and it's closing from the unglamorous end, which is exactly how you know it's real.

Bottom line: The agentic web doesn't arrive with a keynote. It arrives as an MCP server that deletes a checklist. Watch the boring parts disappear first.