---
title: "MCP for business integrations: what it changes and what it does not | FWS Blog"
canonical: "https://flyingweb.ie/insights/mcp-business-integrations-explained"
language: "en"
lastModified: "2026-10-05T12:26:23.043Z"
---

[Connected systems](<https://flyingweb.ie/insights/category/connected-systems/>)

# MCP for business integrations: what it changes and what it does not

Model Context Protocol is becoming part of enterprise automation. Understand the connection it provides, the permissions it still needs and how to trial it safely.

[Flying Web Solutions](<https://flyingweb.ie/about/>)3 October 20264 min read

![An assistant uses a permitted read-only MCP inventory lookup and receives stock information.](<https://flyingweb.ie/uploads/Hn9l1zRx6E0Hz9FuN_DQv-fws-mcp-business-integrations-explained-balanced-v4.webp>)

Illustrative editorial visual.

Put it into practice

One process. A clear scope. A fixed price before we start.

[Discuss your workflow](<https://flyingweb.ie/contact/#book>)

## The practical answer

MCP provides a standard way for an AI application to discover and call connected capabilities. It does not fix poor records, replace the underlying business system or decide which actions your organisation should authorise.

## Why MCP is a current business topic

The Model Context Protocol maintainers released a [new specification on 28 July 2026](<https://blog.modelcontextprotocol.io/posts/2026-07-28/>), including changes to transport, caching and authorisation. UiPath then announced a [native MCP connector in its September platform update](<https://www.uipath.com/newsroom/uipath-platform-updates-fusion>). 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](<https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro>) 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.

AI applicationInterprets the request and selects an offered capabilityWhich tools can it choose from?MCP connectionProvides the agreed interface to those capabilitiesWhich protocol versions and authentication methods are supported?Business systemEnforces the real operation and record permissionsWhat can this identity read or change?Your processDefines approval, ownership and recoveryWho is responsible when a result needs a decision?

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](<https://modelcontextprotocol.io/docs/2026-07-28/tutorials/security/security_best_practices>) 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](<https://flyingweb.ie/what-we-do/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.

1. [MCP: July 2026 specification release](<https://blog.modelcontextprotocol.io/posts/2026-07-28/>)  
   28 July 2026
2. [Model Context Protocol: Introduction](<https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro>)  
   2026-07-28 specification
3. [MCP: Security best practices](<https://modelcontextprotocol.io/docs/2026-07-28/tutorials/security/security_best_practices>)  
   Documentation checked 3 October 2026
4. [UiPath platform update](<https://www.uipath.com/newsroom/uipath-platform-updates-fusion>)  
   23 September 2026

Published by [Flying Web Solutions](<https://flyingweb.ie/about/>), Cork, Ireland. Examples are illustrative unless a named source is provided.

[Back to all insights](<https://flyingweb.ie/insights/>)

Keep reading

## More useful ideas.

[![Routine delivery completes automatically; an exception enters investigation and approval.](<https://flyingweb.ie/uploads/CItC1ojw2TcGjdjwLr-BN-fws-ai-agents-vs-workflow-automation-balanced-v4.webp>)AI at workAI agents vs workflow automation: what should an SME use?Choose between predictable automation, AI-assisted workflows and autonomous agents using the task, the risk and the evidence, not the label.4 min read](<https://flyingweb.ie/insights/ai-agents-vs-workflow-automation>)[![Independent Irish food business preparation area after closing. Laptop with a restrained stock summary, original stock sheets and neatly organised ingredients, stainless steel prep table, warm evening lighting. No people or hands.](<https://flyingweb.ie/uploads/sQol9Y40b8Eqlvsbp0XsN-fws-ai-adoption-ireland-2026-small-business-balanced-v4.webp>)AI at workAI adoption in Ireland: a practical 30-day plan for SMEsThe latest CSO figures show uneven AI adoption. Use a small, measured pilot to decide what helps your own team rather than chasing a national average.4 min read](<https://flyingweb.ie/insights/ai-adoption-ireland-2026-small-business>)[![Close-up still life of a supplier invoice, purchase order and delivery note, one discrepancy marked with a muted coral circle beside a laptop document extraction preview. Practical accounting desk, side window light. No people, hands or payment confirmation.](<https://flyingweb.ie/uploads/GxaLKMK3UFl0KAvIoB94Z-fws-invoice-document-automation-validation-balanced-v4.webp>)Workflow automationInvoice document automation: build a reviewable workflowExtracting invoice fields is only the first step. Learn how validation, duplicate checks and clear approval turn documents into reliable business records.4 min read](<https://flyingweb.ie/insights/invoice-document-automation-validation>)
