Check What the MCP 2026-07-28 Spec Changes for Your Automation Setup

What changed?

This is based on Anthropic's official blog, checked on 2026-10-08.

What does it mean for automation?

If long-running work (Tasks) is standardized as an extension, you can build setups that split slow processing into several steps and hand them off consistently. Being able to put servers on serverless is welcome for small-scale operations because it can cut cost and management burden. How much it actually saves depends on your setup, though, and the original gives no figures.

What does Claude provide?

• More than 950 MCP servers listed in the connector directory
• MCP Apps: servers show interactive UI inside the conversation
• Enterprise-managed authentication: admins deploy connectors across the organization through their IdP
• An observability dashboard for developers: adoption, errors, latency, and usage by product
• MCP tunnel (research preview): connects servers inside a private network without exposing them to the public internet

How do you check the servers and clients you use now?

First, list which spec version each MCP server and client you use supports. Support timing differs by product, so look separately at the announcements for the client you use. A stateless core affects server architecture. A server that relies on session state may need to change so that it receives the information it needs with each request. Do not migrate everything at once; test lower-risk servers first, such as read-only tools.

Who decides permissions and approvals?

Limit the data an automation server can access and the actions it can run to the minimum scope, and check that the authentication method fits your organization's accounts. When managed authentication is available, admins deploy connectors at the organization level through the IdP, and users are connected automatically at first sign-in. As convenient as that is, you need approval criteria for which connectors to allow for whom, and usage monitoring. Errors and latency in the observability dashboard are clues to whether the automation is actually stable.

Which risks should you reduce first?

A server connected to automation runs work for you that no person checks each time. Check whether tools with write permission include hard-to-undo actions such as deleting or sending, and add a human approval step if needed. Authentication aligning with OAuth 2.0 and OIDC does not by itself make your permission design safe.

After adoption, open the logs regularly and look for unintended calls. The spec may be revised, so before implementing, check the original blog and the latest version of the official MCP spec documentation once more.