Skip to main content

Microsoft.Extensions.AI–Part VII–MCP integration

Our journey continues, as we keep finding new features to explore in the Microsoft.Extensions.AI library. Today we have a look at the support for MCP.

This post is part of a blog series. Other posts so far:

What is MCP?

I know, I know, you should have been hiding under a rock if you have never heard about MCP before. But just in case; MCP (Model Context Protocol) is an open protocol developed by Anthropic that provides a standardized way to connect AI models to different data sources and tools.

This allows us to use tool calling without having to build our own plugins (as I demonstrated in Part III of this blog series).

Using MCP with Microsoft.Extensions.AI

The first thing you need is an MCP server. Today there are typically 2 ways that an MCP server can exchange information:

  • Standard Input Output (STDIO)
  • Streamable HTTP

Remark: The Streamable HTTP option replaces the HTTP+SSE transport from protocol version 2024-11-05. You can optionally still use Server-Sent Events (SSE) to stream multiple server messages.

I will be using Streamable HTTP in this example with the Playwright MCP server.

  • Start the server by executing the following command:

npx @playwright/mcp@latest --port 8931

  • Now open your project and add the following NuGet package:

dotnet add ModelContextProtocol

  • Next step is to instantiate an MCP client and get the tools provided by the MCP server:
  • As these tools are instances of McpClientTool, which inherits from AIFunction, we can pass them directly in as ‘plugins’ to our ChatOptions:

That’s all that we need to do!

More information

Tool calling using MCP with Semantic Kernel

Overview | MCP C# SDK

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more