PhyseaWiki How AI actually works Papers physea.ai →

Tool use & MCP

What problem does the Model Context Protocol solve?

With M models and N tools, tool use forced roughly M times N fragile custom integrations. MCP collapses that: a tool exposes itself once, and any MCP-aware model can use it, like a USB-C port for AI.

Last updated 2026-06-15 · Physea Labs

Tool use works, but it created a mess. Every model had its own way of describing tools, and every tool needed wiring for every model. With M models and N tools you face roughly M times N custom integrations, each one fragile and bespoke.

The Model Context Protocol, introduced by Anthropic in late 2024, is an open standard that collapses that.[1] Instead of a custom connector per pair, a tool exposes itself once over MCP, and any MCP-aware model can use it. The official documentation frames MCP as a standard way to connect AI applications to external systems.[2] The common shorthand is that MCP is a USB-C port for AI: one plug, not a drawer of cables.

WITHOUT A STANDARD — M×N Model A Model B Model C Files Email Calendar 9 custom connectors WITH MCP — ONE PORT Model A Model B Model C MCP Files Email Cal. one protocol
Without a standard, every model needs a custom connector to every tool (M×N). MCP is the one shared port.

References

  1. Introducing the Model Context Protocol — Anthropic
  2. Model Context Protocol — Introduction — Model Context Protocol

Related