MCP as a product surface
A travel API provider can offer curated MCP capabilities to several AI hosts, but automatic OpenAPI conversion is only a starting point. Product quality depends on task-level semantics, tenant isolation, delegated identity, stable output schemas and predictable failures.
The MCP adapter should remain separate from the API core. Registry metadata supports discovery; it does not establish code safety, commercial authority or entitlement to a supplier account.
Compatibility and lifecycle
The provider maintains a client and protocol-version matrix, tests capability negotiation and treats descriptions and schemas as behavioural contracts. Changes that appear syntactically compatible can still alter model tool selection.
Enterprise evidence includes conformance and security tests, per-capability telemetry, service objectives, deprecation policy, controlled rollout and the ability to disable one capability without withdrawing the complete service.