Protocols

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.

1 minNora (host) · Theo (expert)
0:00 / 1:21

Transcript

  1. Nora

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

  2. Theo

    Hello everyone!

  3. Nora

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

  4. 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.

  5. Nora

    Who talks to whom?

  6. 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.

  7. Nora

    Where does a bank fit?

  8. 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.

  9. Nora

    So the protocol keeps the payment safe?

  10. 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.

  11. Nora

    Which version should a builder read?

  12. 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.

  13. Nora

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

  14. Theo

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

No ratings yet