our blog

Model Context Protocol: What Happens When AI Starts Talking To AI

It’s early days, but there’s a shift happening in how AI systems exchange information and it could be as transformative as the API economy was for software.

Right now, most large language models (LLMs) work in isolation. They generate answers based on prompts, but lack persistent memory or shared understanding with other systems. If you want different models or agents to work together, you typically need to stitch them with custom logic, manual context passing and a lot of prompt engineering.

That’s where Model Context Protocol (MCP) comes in. Still in its early stages, MCP is starting to define a common structure for how models can pass memory, metadata and context to each other - directly, without a human middle layer. Think of it like an API, but for model to model communication. But instead of endpoints and payloads, it’s about shared understanding and stateful collaboration between AIs.

This matters because, without context, models can’t build on each other’s thinking. They start from scratch with every prompt. But with MCP, you introduce a way to carry forward intent, constraints, even goals which can enable more meaningful multi agent systems. In theory, that could unlock new patterns: agents that collaborate on complex tasks, delegate decisions, or learn continuously from shared experience.

It’s not there yet. MCP is still forming - a concept more than a standard. But like the early days of APIs, there’s a sense that something foundational is emerging. A protocol that could enable AI systems to speak the same language, without needing us to mediate.

It might take time to materialise and the practical use cases aren’t fully known. But if it plays out, the implications are big, not just faster AI development, but entirely new ways of thinking about distributed intelligence.

We’ll be watching closely. Because the moment AIs can truly talk to each other, with memory, intent and shared context - is the moment the paradigm actually shifts.

spread the word, spread the word, spread the word, spread the word,
spread the word, spread the word, spread the word, spread the word,
Illustration representing AI-native product development, combining AI capabilities with traditional software through deliberate product design.
AI

Adding AI Features Doesn’t Make a Product AI-Native

Illustration representing AI software development, engineering expertise, context engineering and accountable decision-making.
AI

Own the Answer: Why AI Software Development Needs Engineering Expertise

Illustration representing AI product design, design systems, expertise and decision-making.
AI

Encode the Judgement: Why AI Product Design Needs More Expertise, Not Less

Conceptual illustration of AI product strategy, experimentation and product decision-making.
AI

Build to Learn: How AI Is Changing Product Strategy

Conceptual illustration of AI software development, highlighting validation, trust and production-ready software.
AI

The Validation Surface: Why AI Software Development Speed Depends on Trust

Adding AI Features Doesn’t Make a Product AI-Native

Illustration representing AI-native product development, combining AI capabilities with traditional software through deliberate product design.
AI

Adding AI Features Doesn’t Make a Product AI-Native

Own the Answer: Why AI Software Development Needs Engineering Expertise

Illustration representing AI software development, engineering expertise, context engineering and accountable decision-making.
AI

Own the Answer: Why AI Software Development Needs Engineering Expertise

Encode the Judgement: Why AI Product Design Needs More Expertise, Not Less

Illustration representing AI product design, design systems, expertise and decision-making.
AI

Encode the Judgement: Why AI Product Design Needs More Expertise, Not Less

Build to Learn: How AI Is Changing Product Strategy

Conceptual illustration of AI product strategy, experimentation and product decision-making.
AI

Build to Learn: How AI Is Changing Product Strategy

The Validation Surface: Why AI Software Development Speed Depends on Trust

Conceptual illustration of AI software development, highlighting validation, trust and production-ready software.
AI

The Validation Surface: Why AI Software Development Speed Depends on Trust

Adding AI Features Doesn’t Make a Product AI-Native

Illustration representing AI-native product development, combining AI capabilities with traditional software through deliberate product design.

Own the Answer: Why AI Software Development Needs Engineering Expertise

Illustration representing AI software development, engineering expertise, context engineering and accountable decision-making.

Encode the Judgement: Why AI Product Design Needs More Expertise, Not Less

Illustration representing AI product design, design systems, expertise and decision-making.

Build to Learn: How AI Is Changing Product Strategy

Conceptual illustration of AI product strategy, experimentation and product decision-making.

The Validation Surface: Why AI Software Development Speed Depends on Trust

Conceptual illustration of AI software development, highlighting validation, trust and production-ready software.