# What MCP (Model Context Protocol) is, and why it matters for business AI

Published 22 April 2026 by Spark · Technology, explained · 4 min read
Canonical: https://hellospark.co.uk/writing/what-is-mcp-model-context-protocol

> MCP is a common plug for AI. Instead of building a bespoke connection between every model and every system, you build one standard socket and any compliant model can use it. It sounds like plumbing because it is, and it is the plumbing that decides whether you are locked in or free to switch.

MCP is a standard plug for AI. That is the whole idea, and it is more important than it sounds. Before it, connecting a model to your systems meant building a bespoke bridge for every combination: this model to that document store, that model to your CRM, each one hand-wired and each one a maintenance headache. The Model Context Protocol replaces all of that with a single agreed socket. Build the socket once and any model that speaks the protocol can plug in. It is the difference between a drawer of proprietary chargers and a world where everything takes the same cable.

## The problem it solves

An AI model on its own is a brain in a jar. It can reason about what you type, but it cannot see your files, query your database, or do anything in your systems unless you connect it. Historically every one of those connections was custom work. Ten tools and three models meant a tangle of one-off integrations, each of which broke when anything changed. It was slow to build, expensive to maintain, and it quietly chained you to whichever vendor you had wired everything to.

MCP, introduced by Anthropic and now adopted well beyond it, sets a common language for these connections. You expose your tools and data through an MCP ‘server’, which is just a standard adapter for one system. Any model that acts as an MCP ‘client’ can then use it. Build the adapter for your document store once, and Claude, or any other compliant model, can read from it without further work. The tangle collapses into a set of reusable parts.

## What it actually connects

Two things, mostly. Tools, meaning actions the model can take, such as searching your files, querying a database, or raising a ticket. And context, meaning information the model can read to do its job. An MCP server for your practice management system might let the model look up a matter, read the file notes, and draft a next step, all through one standard interface rather than three bespoke ones. The model still only does what you permit, and every action can be logged, which matters when a supervisor later asks what it touched.

## Why it reduces lock-in

This is the part that should interest anyone running a firm. When your integrations are bespoke to one vendor’s model, switching models means rebuilding everything, so in practice you never switch, and you have handed a supplier real power over you. When your integrations speak MCP, they are not tied to any single model. The connective tissue you paid to build stays yours. If a better or cheaper model arrives next year, you point your existing servers at it and carry on. In a field moving as fast as this one, the freedom to change your mind without a rebuild is worth real money.

We think this matters enough to treat as a design principle. We build integrations to open standards wherever we can, so the value sits in your systems and your processes rather than in a dependency you cannot escape. That is not idealism. It is the same instinct any sensible firm applies to outsourcing: do not let one supplier hold the only key.

## What it is not

MCP is not artificial intelligence, and it is not a product you buy. It is a protocol, a set of rules for how software talks to software, in the same family as the standards that let any browser open any website. It does not make a model cleverer. It makes a model connectable. And it does not remove the need for governance. A standard socket makes it easier to plug AI into sensitive systems, which means the questions of who approved this, what data does it touch, and who is watching it become more pressing, not less. Convenience and control have to grow together.

## Why a non-technical leader should care

You will not write a line of MCP, and you should not need to. But the decisions made around it shape two things you do own: how much a future model switch costs, and how much of your AI value stays inside your firm rather than trapped in a vendor. When a supplier proposes an AI build, one good question is whether the integrations are proprietary or standards-based. The honest ones will welcome the question. The answer tells you whether you are buying an asset or renting a cage.

We build with tools such as Claude precisely because they take this open approach seriously, and because it keeps your options open as the field moves. If you want a build that connects to your systems without chaining you to one vendor, that is exactly how we work. [Book a review](/book-a-review) and we will map what a standards-based integration would look like for your firm, and what it saves you the day you decide to switch.
