Most large companies now operate combinations of enterprise resource planning systems, transportation management systems, warehouse management systems, planning applications, supplier portals, control towers, data platforms, and specialized analytics tools. Yet employees still spend substantial time searching for information, reconciling records, moving data between applications, and coordinating work through email and spreadsheets.

Artificial intelligence agents could change this operating model.

An agent can interpret a request, gather information, select tools, complete a sequence of tasks, and adjust its behavior based on the result. Instead of merely answering a question, it could investigate a late shipment, determine the likely cause, evaluate alternatives, and prepare a recommended response.

But agents cannot operate effectively if every enterprise system speaks a different technical language.

This is why Model Context Protocol, or MCP, could become important to the next generation of supply-chain architecture.

MCP is an open protocol designed to standardize how AI applications connect to external data, tools, and systems. It provides a common method for exposing information and capabilities to AI models without requiring a unique integration for every model, application, and data source.

If AI agents are to become useful in supply-chain operations, they need a consistent way to discover available resources, retrieve the correct context, and invoke approved actions. MCP is one possible mechanism for creating that layer.

The Integration Problem Behind Enterprise AI

Large language models can summarize documents, generate explanations, and reason over text. On their own, however, they do not know the current status of an order, inventory position, shipment, supplier, production schedule, or customer commitment.

That information lives in ERP databases, planning platforms, carrier portals, warehouse systems, supplier-risk services, document repositories, and custom applications.

To become operationally useful, a model must reach those systems.

Early enterprise AI implementations have generally relied on custom integrations connecting a model to a database, API, search service, or software platform. This can work for a narrow use case, but problems appear when companies attempt to scale.

If an organization uses several AI models, dozens of systems, and a growing number of agent workflows, integration complexity rises quickly. Security rules may differ across projects. Tool definitions become inconsistent. Updates to one system may break multiple agents. Governance becomes difficult because no common layer controls how AI applications interact with enterprise resources.

MCP attempts to reduce this many-to-many problem by introducing a standardized interface between AI applications and external systems.

What MCP Actually Does

MCP uses a client-server architecture.

An AI application acts as the client. External systems, tools, or data sources are represented through MCP servers. Each server exposes a defined set of resources and capabilities that an authorized AI application can discover and use.

An MCP server describes the data and executable tools an authorized AI application can use.

An agent investigating a delayed customer order might use one server to retrieve order details, another to obtain shipment status, another to review inventory at alternative facilities, and another to calculate expedited transportation options.

None of this is impossible without MCP. These capabilities can be built through conventional APIs, middleware, and integration platforms.

The potential value is standardization.

A common protocol could make it easier to expose enterprise capabilities to multiple AI systems while maintaining a consistent access and control layer.

From Chatbots to Operational Agents

Many current enterprise AI deployments are conversational interfaces placed over existing information.

A user asks a question. The system retrieves content. The model generates a response.

That can improve productivity, but it does not fundamentally change the operating model.

Agentic systems go further. They can break a goal into tasks, select tools, execute steps, inspect results, and continue until they reach a stopping condition.

Consider a critical component expected to arrive three days late.

A conventional alert may notify a planner, who then needs to confirm the delay, identify affected production orders, check inventory, assess substitutes, review alternative suppliers, evaluate expedited freight, estimate customer impact, and coordinate a recovery plan.

An agent could assemble much of this analysis. It might retrieve shipment status, query the production schedule, calculate days of supply, identify affected orders, and prepare several recovery options.

The human planner would retain critical decision authority but receive a structured recommendation instead of beginning with fragmented information.

For this to work, the agent needs reliable access to many different applications and data sources.

That is where MCP becomes strategically relevant.

An AI-Facing Access Layer

Traditional integration platforms focus on moving data and coordinating transactions among systems.

MCP addresses a different layer. It helps an AI application discover and use tools in a format designed for model-driven interaction.

That distinction matters because an agent does not always follow a fixed workflow. It may choose different tools depending on the problem.

Different disruptions require different tools and responses. The agent must understand which tools exist, what inputs they require, and what outputs they provide.

An MCP server can expose those capabilities in a consistent, machine-readable format.

This does not eliminate APIs, middleware, master-data systems, or integration platforms. In many cases, the MCP server will sit above those capabilities.

It becomes an AI-facing access layer: a method for making existing enterprise architecture legible and usable to agents.

A Modular Supply-Chain Architecture

The long-term potential becomes clearer when MCP servers are viewed as reusable enterprise building blocks.

Transportation, warehouse, planning, and supplier servers could expose approved capabilities such as shipment status, inventory, forecasts, capacity, risk indicators, and optimization tools.

Once standardized, the same capabilities could serve procurement, planning, logistics, and customer-service agents. This reduces duplicate integrations and supports a more modular architecture.

Specialized Agents Are More Realistic

The most credible enterprise future is unlikely to involve one all-powerful agent controlling the entire supply chain.

Supply chains are too complex, specialized, and consequential for that model.

A more realistic architecture consists of multiple agents with bounded responsibilities. A company might deploy a transportation-exception agent, supplier-risk agent, demand-planning agent, warehouse-labor agent, procurement agent, and production-scheduling agent.

Each agent would have access only to the tools and information required for its role.

A transportation agent might retrieve rates and recommend carrier changes but lack authority to change supplier payment terms. A procurement agent might analyze supplier performance and prepare a sourcing event but be unable to release production orders.

Specialized agents will also need to coordinate. A supplier disruption may begin as a procurement problem, become a planning issue, trigger a transportation requirement, and ultimately affect customer service.

MCP helps agents interact with tools and systems. Agent-to-agent protocols are intended to help agents exchange tasks and context with one another.

Together, these technologies could support a layered architecture in which enterprise systems hold operational records, integration platforms connect those systems, MCP servers expose approved capabilities, specialized agents perform bounded tasks, and humans retain decision authority.

This is not a fully autonomous supply chain. It is structured machine-assisted coordination.

Why Software Vendors Should Pay Attention

In an agentic environment, users may interact less frequently with application screens. An agent could call planning, inventory, transportation, and supplier capabilities in the background.

Vendors must therefore decide which functions they expose, how they secure them, and whether they support open protocols or proprietary frameworks. Competitive advantage may increasingly depend on making capabilities easy to discover, govern, and combine with other systems.

Governance Will Determine Whether This Works

The promise of MCP should not obscure the risks.

An agent with access to enterprise tools can cause operational damage if permissions, validation, and monitoring are weak. A mistaken tool call could change an order, expose confidential information, select an inappropriate carrier, or initiate an unauthorized transaction.

Companies will need strict controls around identity, authentication, authorization, data exposure, tool permissions, audit trails, and human approval.

Read access should be separated from transaction authority. High-impact actions should require approval. Tool outputs should be validated before they are used in subsequent steps.

Organizations must also defend against prompt injection, malicious tool descriptions, compromised servers, and incorrect model reasoning.

MCP can standardize access, but it does not make that access inherently safe.

A Practical Path Forward

Supply-chain leaders do not need to redesign their enterprise architecture around MCP immediately.

A practical starting point is one bounded workflow with measurable value and limited operational risk.

A transportation exception, supplier document review, order-status investigation, or inventory inquiry may be more appropriate than autonomous procurement or production scheduling.

The company can expose a small number of approved tools, establish permissions, test the workflow, and measure both operational performance and control effectiveness.

The objective is not to deploy agents everywhere. It is to learn where standardized tool access reduces integration effort and improves decision speed.

MCP may not become the dominant protocol, but the broader architectural direction is difficult to ignore.

AI models are moving beyond isolated chat interfaces. They are beginning to interact with the systems where operational work occurs.

For supply-chain organizations, the strategic question is no longer whether AI can generate useful answers. It is whether agents can access the right data, use the right tools, and act within the right controls.

Protocols such as MCP could provide part of that foundation.

The companies that prepare their systems, permissions, and workflows for this environment will be better positioned to move from AI experimentation to operational value.

The post Model Context Protocol and the Future of Agentic Supply Chains appeared first on Logistics Viewpoints.

Weekly highlights

The Freightos Weekly Update is on hiatus this week – but we’ll be back next week!

In the meantime, here are this week’s changes to freight rates on some of the major lanes.

Ocean rates – Freightos Baltic Index

Asia-US West Coast prices (FBX01 Weekly) decreased 12% to $6,212/FEU.

Asia-US East Coast prices (FBX03 Weekly) decreased 1% to $9,002/FEU.

Asia-N. Europe prices (FBX11 Weekly) decreased 3% to $5,575/FEU.

Asia-Mediterranean prices (FBX13 Weekly) decreased 2% to $6,697/FEU.

Air rates – Freightos Air Index

China – N. America weekly prices decreased 2% to $5.76/kg.

China – N. Europe weekly prices decreased 10% to $3.84/kg.

N. Europe – N. America weekly prices stayed level at $1.93/kg.

Freightos Terminal: Real-time pricing dashboards to benchmark rates and track market trends.

The post Freight rate update for July 29th – July 29, 2026 Update appeared first on Freightos.

For the past several years, the artificial intelligence infrastructure market has followed a simple imperative: build as much computing capacity as possible, as quickly as possible.

Cloud providers ordered graphics processing units in extraordinary volumes. Technology companies committed billions of dollars to new data centers. Utilities received requests for power loads comparable to those of entire cities. Investors rewarded companies positioned anywhere along the AI infrastructure supply chain.

That expansion is not ending. What is changing is the standard by which it will be judged.

The first phase of the boom was defined by scarcity. Companies needed access to advanced chips, networking, cloud capacity, power, land, and technical talent. The strategic risk was failing to build enough capacity while competitors moved ahead.

The next phase will be defined by utilization, economics, and execution.

Investors, customers, and corporate boards will ask harder questions. How much capacity is productive? Which workloads justify premium computing resources? How quickly can new facilities be energized? Where is the revenue? Who bears the risk when technology, demand, and infrastructure timelines do not align?

AI capital spending is becoming a supply-chain and asset-productivity challenge.

The Spending Has Not Stopped

The largest cloud and technology companies continue to spend heavily on data centers, servers, networking, power systems, cooling, and specialized processors.

But scale does not guarantee that every investment will earn an adequate return.

During the first stage of generative AI adoption, access to computing capacity was itself a competitive advantage. Advanced accelerators were scarce, cloud providers rationed access, and companies paid premium prices to train models and launch services.

Under those conditions, the case for more infrastructure appeared almost self-evident. If capacity could be built, demand would likely fill it.

That assumption is now being tested.

AI-related cloud revenue is growing, but the infrastructure required to support it is expanding even faster. This does not prove that spending is excessive. Infrastructure investment often precedes revenue by years.

It does mean that the burden of proof is changing. Management teams must show not merely that AI demand exists, but that expensive assets can be deployed, utilized, and monetized quickly enough to support their financing, depreciation, operating, and energy costs.

Transformative Technology Can Still Produce Bad Investments

The debate is often framed too simply. It is not a choice between believing that AI will transform the economy and believing that some infrastructure will be overbuilt. Both can be true.

AI adoption may continue to expand while some data centers, cloud contracts, and financing structures produce disappointing returns. Capacity may be built in the wrong locations, arrive before sufficient power is available, or become economically outdated faster than expected.

The decisive questions are more specific:

Which AI workloads will generate durable demand?

How much capacity will support training versus inference?

How quickly will computing efficiency improve?

Which providers will retain pricing power?

How long will current hardware remain economically competitive?

Inference Must Sustain the Next Phase

The early infrastructure boom was propelled by training increasingly large foundation models. Training requires enormous accelerator clusters, high-bandwidth networks, large datasets, and sophisticated cooling and power systems.

Inference—the operation of trained models to answer questions, analyze data, control agents, and support applications—could create a broader and more durable market. Its economics, however, are different.

Enterprise users care about latency, reliability, privacy, accuracy, and cost per transaction. They do not need the largest model or most advanced processor for every task.

A supply-chain application classifying documents may require far less computing power than an agent analyzing a global disruption. A forecasting assistant may combine machine learning, retrieval, optimization, and a smaller language model rather than invoke a frontier model for every interaction.

As enterprise architectures mature, companies will become more selective about where they use premium computing.

The next phase will reward providers that match each workload to the appropriate model, processor, memory configuration, network, and service level. The objective will shift from maximizing raw compute to optimizing useful compute.

Utilization Becomes the Critical Metric

AI infrastructure is expensive before it produces a single output.

A functioning cluster requires accelerators, servers, memory, networking equipment, storage, power distribution, backup generation, cooling, buildings, land, security, and connections to telecommunications and electricity networks.

Advanced processors may remain technically useful for years, but their economic attractiveness can decline quickly when new generations deliver better performance per watt or lower inference costs.

An underutilized warehouse can sometimes wait for demand. An underutilized AI cluster may become less competitive while it waits.

Providers need enough capacity to meet bursts of demand and maintain reliability, but idle accelerators still consume capital. High utilization improves economics, while utilization near physical limits reduces flexibility and complicates maintenance.

It will also create demand for better workload orchestration. Computing tasks may be scheduled according to urgency, energy availability, service levels, processor type, and location. Noncritical workloads may shift to periods when electricity is cheaper or the grid is less constrained.

Power Is Becoming the Primary Constraint

The AI industry can manufacture more chips, raise more capital, and build larger models. It cannot instantly create transmission lines, substations, transformers, generating capacity, and grid interconnections.

The immediate problem is regional concentration. Data centers may represent a manageable share of global electricity demand while placing severe pressure on particular local power systems.

Site selection is therefore becoming a strategic sourcing decision.

The best location is no longer simply the one with inexpensive land, favorable taxes, and fiber access. Developers must evaluate electrical capacity, interconnection timelines, transmission constraints, long-term power pricing, water availability, weather exposure, permitting, community opposition, labor availability, and proximity to users and networks.

In some cases, power supply must be developed alongside the data center. Technology companies are examining renewable energy, batteries, natural gas generation, nuclear power, utility agreements, and dedicated generation.

Regions that can provide reliable power, equipment, permitting, and skilled labor may attract the next generation of AI investment. Those that cannot may lose projects regardless of their technology talent or access to capital.

Data Centers Are Becoming Industrial Megaprojects

The scale of proposed AI campuses is moving them beyond the traditional data-center model.

A multi-gigawatt campus resembles a major industrial development requiring coordination among technology providers, utilities, equipment manufacturers, construction firms, financiers, regulators, and communities.

These projects combine large capital requirements, long equipment lead times, interdependent schedules, changing technical specifications, complex permitting, scarce specialized labor, and uncertain demand forecasts.

A delay in one element can strand the others. A facility may be structurally complete but unable to secure electricity. Processors may arrive before cooling systems are ready. Grid equipment may be delayed. New chips may require changes to power density or thermal architecture.

The supply chain must therefore be managed as an integrated program rather than a sequence of independent procurement decisions.

Financing Will Face Greater Scrutiny

The largest cloud companies can finance substantial investment from their balance sheets. But the scale of the buildout is creating more complex arrangements among infrastructure funds, developers, utilities, chip suppliers, sovereign investors, cloud providers, and AI companies.

A developer may build the facility. A utility may finance grid upgrades. A cloud provider may sign a long-term lease. An AI company may commit to capacity it expects future customers to consume.

Customers may renegotiate, delay deployment, encounter financing problems, or find that technological progress changes their capacity requirements. Investors must therefore ask who guarantees the commitments, who funds power upgrades, what happens if energization is delayed, and whether the facility can serve another customer.

These are infrastructure-finance questions, not merely technology questions.

Enterprise Buyers Will Become More Disciplined

Many enterprises have moved beyond experimentation but have not yet achieved broad production deployment. They are focusing more closely on return on investment, governance, workforce readiness, and the practical requirements of scale.

Supply-chain organizations face a demanding business case.

An AI assistant that drafts marketing copy can generate value even when its output is imperfect. An AI agent changing replenishment parameters, selecting a carrier, releasing an order, or responding to a disruption operates in a much less forgiving environment.

Companies must connect AI to trusted data, transactional systems, optimization engines, decision rules, and human approval structures. The strongest use cases will be tied to measurable outcomes such as lower transportation expense, reduced planner workload, faster exception resolution, improved inventory availability, lower expedite costs, reduced downtime, and higher warehouse productivity.

The next phase will favor projects that produce operational results rather than merely demonstrate generative capabilities.

The Opportunity Is Moving Up the Stack

The first infrastructure wave rewarded semiconductor designers, foundries, memory manufacturers, networking suppliers, server vendors, and cloud providers.

The next layer of value will increasingly come from making infrastructure productive.

That includes workload orchestration, model routing, inference optimization, energy management, cloud cost control, AI governance, enterprise integration, and industry-specific applications.

The enterprise does not ultimately want computing capacity. It wants better decisions and improved execution.

A company may use multiple models, cloud providers, private environments, specialized processors, and agent frameworks. The winning platforms will coordinate those resources while maintaining security, visibility, and economic control.

This Is a Transition, Not a Collapse

There are legitimate reasons to be cautious. Capital requirements are rising. Power constraints are real. Some companies will struggle to turn capacity into profitable services. Hardware may depreciate economically faster than expected, and financing structures may weaken if demand assumptions fail.

But increased scrutiny does not mean AI infrastructure demand is disappearing.

The market is moving from indiscriminate expansion toward differentiation.

Projects with reliable power, strong customers, flexible architectures, disciplined financing, and high utilization will remain valuable. Projects built around speculative demand, weak counterparties, unrealistic energization schedules, or inflexible technology assumptions will face greater pressure.

The first phase rewarded access to capital and computing. The next phase will reward execution.

For supply-chain leaders, the lesson is familiar: growth does not eliminate the need for operational discipline. It makes that discipline more important.

The AI infrastructure buildout is continuing, but capacity alone is no longer the objective. The challenge is to convert unprecedented investment in chips, power, and data centers into dependable, economically productive intelligence.

The post AI Infrastructure Is Entering Its Next Phase appeared first on Logistics Viewpoints.