New MCP specification addresses the main barrier to enterprise adoption

The hope is that the changes, detailed in the protocol’s documentation, will make widespread deployment in an enterprise context much easier. MCP started as something that simply ran on a local machine, connecting models to local apps, so the new spec is a major rethink of some of its foundations.

There is also a new deprecation policy that ensures at least 12 months between when a feature’s formal deprecation is enacted and when the feature may actually be removed—with a narrow exception for critical security updates. This is again in keeping with the general “let’s make this work better at enterprise scale” theme of the new specification.

MCP is

→ Continue reading at Ars Technica

Share article

All Categories