The new MCP standard: what changes for Claude connectors

On July 28 a new version of MCP shipped, the open standard Claude uses to connect to outside services. It's what powers connectors: those "Connect" buttons that let Claude reach your mail, calendar, drive or Notion base. The news looks technical, but it decides something simple: how many services you can plug into Claude, and how often they drop out mid-task.

What is MCP, and what does it have to do with connectors?

MCP (Model Context Protocol, an open protocol linking AI to external programs and data) is a shared socket. Without it, every service would have to be wired into every AI by hand, separately. With it, a service builds one connector that works in Claude and in other apps that support the standard.

The scale is no longer a toy: Claude's connector directory lists over 950 MCP servers, and library downloads grew fourfold over the year to 400M a month (Anthropic announcement, July 28).

What exactly changed on July 28?

This is the fifth spec release, and three of its changes matter even from a business owner's altitude (the MCP team's breakdown):

• The connection is now stateless. Claude and the service used to hold an open session, and a drop meant bringing the connector back up. Now each request stands on its own and can land on any free server. For you that's reliability: fewer hung connections on long tasks.
• Interfaces inside the conversation. The MCP Apps extension is formally part of the standard: a service can render a live interactive block right in the chat instead of sending you to another tab. Tasks, the mechanism for long background work, landed alongside it.
• Login by normal corporate rules. Authorization now lines up with OAuth 2.0 and OIDC (the sign-in standards behind Entra and Okta), so hooking up work services stops being a separate adventure. There's also a formal deprecation policy: a twelve-month minimum to migrate, instead of things breaking on a Thursday.

The announcement also mentions MCP tunnels in research preview: a way to give Claude access to a company's internal services without exposing them to the public internet.

When will I notice this in my Claude?

Not today. Anthropic says support is rolling out across Claude products gradually. Nothing moved in the interface, connected connectors work as before, and there is nothing to update by hand.

The value is in the next few months. The easier and cheaper it is to build and run a connector, the faster the things you actually need show up in the directory: your bank, CRM, inventory system, industry service. So the takeaway isn't "go update", it's "check what you can already connect".

What to do with your connectors now?

1. Open Claude or the Claude app, click "Customize" in the left sidebar, the Connectors tab, the "+" button, then "Browse connectors" (Claude Help Center guide).
2. Look for the services your work actually lives in, not the ones that are fashionable to connect. Mail, calendar, drive and a task tracker cover most of the routine.
3. Connect them one at a time and immediately give Claude a task on your own data. A connector without a task is just a checkbox in settings.
4. If a contractor is building you an internal server, ask them to target the 2026-07-28 version: older servers will need reworking.

We cover connectors, skills and automations hands-on, not in theory: free guides and the first lesson with no signup. Related and recent: Record a skill, where Claude learns a task from your screen recording.

AGINE Academy is an independent product, not affiliated with Anthropic. Claude is a product of Anthropic.