The protocol outlived the product

A vendor's integrated tool layer switches off in nine days. The open protocol that competed with it has over a thousand servers. This sequence is not new, and it is not finished.

The Assistants API endpoints stop on 26 August — announced a year ago, due in nine days. Integrations still on it must adopt MCP for external tool connections.

Nine days is the practical story

A year of notice is generous. A year of notice is also exactly how long it takes for a deprecation to be forgotten. Anything still calling those endpoints breaks next week, and it will present as a broken integration, not as a deprecation notice.

Go and grep for it now. That is the entire actionable content of this post.

The structural story is bigger

The Assistants API was an attempt to own the layer above the model — threads, tools, state — as proprietary surface. MCP is an open protocol for the same job. The proprietary surface is being switched off while the open protocol is what every client implements.

Well over a thousand community servers are listed, and Claude Code, Codex CLI and Gemini CLI all speak it, alongside Cursor, Continue, Cody and Zed.

That outcome was not obvious two years ago, and the sequence is familiar: a vendor ships an integrated abstraction, an open protocol standardises the capability, the integrated version erodes because customers will not rebuild per vendor. Tooling standardises even where models do not.

What a thousand servers does not give you

Assurance. A thousand servers is a thousand pieces of third-party code being handed tool-calling authority inside someone's environment, with wildly varying quality and no meaningful review layer between registry and production. Package ecosystems learned this expensively. This one is younger and wired directly to actions.

What this asks of you

Differentiation has left the integration layer. It now sits in what the model does with the tools and in how tightly the agent's authority is bounded — and one government has started writing that boundary into law.

So: audit which MCP servers you actually trust, and write down what each is allowed to do. The protocol won. Nobody won the part about whether it is safe.

First AI Movers — MCP and the Assistants API Sunset: Migrate by August 2026 → · Morph — Best AI Coding Agents (August 2026): Scored Leaderboard →