The stock lookup returns seven of the 20 requested adapters
A customer asks whether 20 adapters are available. The answer sits outside the conversation, in a stock system. We built two small local examples to make the connection understandable: a direct HTTP API and an MCP tool. Both read the same fictional stock file. No language model or customer system was involved.[S3]
A direct API call works when the application knows the operation
Our API client knows the endpoint and supplies a product identifier. It receives seven available units and no delivery date. A real integration also needs the application to understand the response and handle errors. APIs can have machine-readable descriptions too; discovery is not exclusive to MCP.
MCP describes the tools a compatible client can call
In our MCP example, the client first reads the offered tool, get_stock, and its required product identifier. It then calls that tool. MCP standardizes this exchange between compatible clients and servers. A server can call an existing API behind the tool. Our two examples are separate implementations; this MCP server does not call our HTTP API.[S1][S2]
Neither route turns stock into a delivery promise
Both return seven units for the known product and an error for an unknown product. Neither implements reservations. These are chosen behaviours in our programs, not security guarantees of either approach. The customer still needs 13 more adapters and a delivery date. Someone must own the resulting promise.[S3]
Choose the connection for a concrete task
A direct API can suit a defined workflow whose calling application you control. Evaluate MCP when compatible AI applications need a shared way to discover and use offered tools. Check client support, permissions, maintenance and the result the customer actually needs. Our example measures none of those production costs or benefits.
Our chosen tests: three MCP calls across two sessions on 17 October 2026; three HTTP requests on 24 October. Synthetic data, unchanged after the negative cases. No ERP, authentication audit, efficiency or traffic comparison.
For a customer agent using your website, the broader question is whether the whole task succeeds. Explore our Agent Experience work. WebMCP addresses tools in the browser; it is a separate website decision. Agent Experience · WebMCP