Why MCP is a current business topic
The Model Context Protocol maintainers released a new specification on 28 July 2026, including changes to transport, caching and authorisation. UiPath then announced a native MCP connector in its September platform update. These signals show the protocol moving into broader integration tooling.
That does not mean every supplier connection should immediately be rebuilt. If a fixed integration already moves the right record reliably, a new protocol label is not a business reason to replace it. MCP becomes relevant when an AI application needs a consistent way to use a set of permitted capabilities.
A plain-language model of the connection
The official MCP introduction describes a standard connection between AI applications and external systems. An MCP server exposes capabilities such as tools or resources; a compatible client can discover and use what is offered. The business system behind the server still owns its records and operations.
Imagine a stock system offering a narrow capability called “check stock for a product.” An AI assistant can request that capability rather than navigating an entire application. A different capability might create a proposed order. The two operations should have different permissions and consequences.
This is an explanatory model, not a description of a particular product installation. The exact capabilities and controls depend on the client, server and system you choose.
Start with a narrow read-only pilot
A useful first test might answer a stock question, retrieve an approved policy or find the status of a named order. Limit the pilot to the records needed for that task. A broad connector that can see everything makes it harder to understand whether access is appropriate.
Ask the implementer to demonstrate a permitted request, a forbidden request and an unavailable source. Also ask what happens if the model chooses the wrong tool. The interface should make a safe failure understandable instead of silently improvising.
Before adding writes, define the proposed change and the approval route. A draft or proposal can show value while giving the team time to inspect the behaviour. Changing live orders or customer accounts is a different trial with a different quality bar.
Security is still a design responsibility
The MCP security guidance discusses risks including confused-deputy problems and token handling. A standard interface does not remove those concerns. Implementers must use appropriate authorisation and preserve the intended boundary between systems.
- Use a dedicated identity with the minimum access the task needs.
- Keep credentials in approved server-side storage.
- Make read, draft and write capabilities clearly distinct.
- Record important calls and outcomes without unnecessarily copying sensitive content.
- Define how access is revoked and how a failed action is investigated.
These are suggested questions for your project, not a claim that a connector is secure merely because it supports MCP. Check what the actual implementation enforces. A tool name that sounds harmless may still expose a broad operation behind the scenes.
How to decide whether it is worth using
Compare the connection against your existing integration requirements. Does it reduce duplicated adapter work? Is it supported by the systems you intend to keep? Can your team understand the permissions and recover from a failure?
Ask for the total maintenance plan, including protocol upgrades and the business system’s own API changes. The July specification is a reminder that interoperability has a lifecycle; a successful demonstration should be followed by a supportable implementation.
MCP is one option within system integration. Start with the capability the business needs, then choose the interface that makes it reliable and manageable.
Sources and further reading
Primary sources checked on 3 October 2026. Product announcements describe vendor plans and capabilities; availability and results depend on the implementation.
- MCP: July 2026 specification release
28 July 2026 - Model Context Protocol: Introduction
2026-07-28 specification - MCP: Security best practices
Documentation checked 3 October 2026 - UiPath platform update
23 September 2026




