Blog Post

Apps on Azure Blog
2 MIN READ

Smart AI integration with the Model Context Protocol (MCP) ... part 2

Mark Harrison (UK)'s avatar
Jul 04, 2025

What MCP is, including its architecture and core components

A discussion on Model Context Protocol:

  • Part 1 - Why is there a need for MCP Link part 1
  • Part 2 - What MCP is, including its architecture and core components
  • Part 3 - A demo of MCP — including how to configure it so anyone can run it  Link part 3
  • Part 4 - An example of how to develop an MCP server — a potential starter project for connecting to your own knowledge resources Link part 4
  • Part 5 - How to add OAuth authentication/authorization to our MCP Server Link part 5 

Part 2 - What is MCP?

The Model Context Protocol (MCP) is an open standard designed to enable intelligent AI applications to seamlessly communicate and interoperate with a wide range of external tools and services. MCP abstracts away integration complexities by defining a unified, extensible communication layer that supports context-aware interactions.

https://modelcontextprotocol.io/

Overview of MCP

Architecture

MCP is structured around a modular client-server architecture consisting of three primary components:

  • Server: The service or knowledge provider, which exposes functionality or data to external clients.
  • Client: Acts as a communication endpoint, maintaining a 1:1 connection with a specific Server instance. Clients manage the request/response lifecycle and facilitate context exchange.
  • Host: The host manages one or more clients, and provides the MCP-enabled services to the intelligent application

 

 

This design separates concerns cleanly:

  • Resource owners manage Server implementations, controlling service logic and data.
  • Application developers integrate MCP clients into their hosts, enabling plug-and-play extensibility without needing to know about the service internals.

Transport protocols

MCP supports two primary transport mechanisms:

  • Standard In/Out: Designed for local services running on the same machine, leveraging standard input/output streams.
  • HTTP (Streamable): Facilitates remote communication over the web.

Note some documentation referes to SSE (Server-Sent Events) - this has recently been deprecated in favor of standard HTTP streaming.

MCP Ecosystem

The MCP ecosystem is expanding rapidly, with hundreds of compliant services available. Integrating these services into intelligent applications requires minimal configuration.

Catalogs of MCP compliant tools include:

 

---

Link part 3 - A demo of MCP

Mark Harrison https://markharrison.io/ 

Updated Jul 15, 2025
Version 5.0
No CommentsBe the first to comment