---
title: "Model Context Protocol: hosts, clients and servers"
type: podcast episode 1
published: 2026-10-06T06:00:00.000Z
url: https://agenticopenfinance.com/podcasts/wire-2026-10-06
audio: https://agenticopenfinance.com/podcasts/audio/wire-2026-10-06.mp3
voices: synthetic (AI-generated speech)
---

# Model Context Protocol: hosts, clients and servers

> What MCP standardises, how its three roles fit together, and where it sits in a finance flow where an agent reads accounts or drafts payments.

## Transcript

**Nora:** Hi! This is On the Wire, from AgenticOpenFinance™. I'm Nora, here with Theo.

**Theo:** Hello everyone!

**Nora:** Theo, we start the season with MCP. In one sentence, what is it?

**Theo:** The Model Context Protocol is an open protocol for connecting AI applications to outside data and tools, so each integration does not have to be built from scratch.

**Nora:** Who talks to whom?

**Theo:** Three roles. The host is the AI application. Clients are connectors inside it. Servers expose capabilities: resources for data, prompts for templates, and tools the model can ask to run.

**Nora:** Where does a bank fit?

**Theo:** A bank could run a server that offers read-only account data as resources and a payment draft as a tool. The host decides which of those the model can see.

**Nora:** So the protocol keeps the payment safe?

**Theo:** No. It carries requests and results. Its principles ask for explicit user consent and treat tool descriptions as untrusted, but mandates, limits and approvals are yours to build around it.

**Nora:** Which version should a builder read?

**Theo:** The one named by date. We read the version of twenty-eight July twenty twenty-six, and its security principles are worth reading first.

**Nora:** The written version and the details are on the AgenticOpenFinance™ blog.

**Theo:** Our voices were made with AI. See you next week, bye!
