Integrating Model Context Protocol (MCP) Tools with Semantic Ker…
@LiteObject
About Integrating Model Context Protocol (MCP) Tools with Semantic Ker…
A comprehensive .NET demonstration of integrating Model Context Protocol (MCP) tools with Microsoft Semantic Kernel. Features a robust MCP client with 23+ built-in tools, intelligent error handling, and AI-powered tool orchestration. Includes both local .NET MCP server and extern
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Integrating Model Context Protocol (MCP) Tools with Semantic Kernel: A Step-by-Step Guide?
This repository demonstrates how to integrate Model Context Protocol (MCP) tools with Microsoft Semantic Kernel, allowing AI models to interact with external data sources and tools through a standardized interface. It provides a reusable .NET framework with a local MCP server, client application, and configuration system for developers building AI-driven workflows.
How to use Integrating Model Context Protocol (MCP) Tools with Semantic Kernel: A Step-by-Step Guide?
Clone the repository, restore .NET dependencies, optionally set an OpenAI API key via user secrets, and run the demo client with dotnet run --project src/Demo.MCP.Client. The client automatically connects to enabled MCP servers (configured in appsettings.json) and starts an interactive command mode where you can list tools and call them with JSON parameters.
Key features of Integrating Model Context Protocol (MCP) Tools with Semantic Kernel: A Step-by-Step Guide
- Automatically connects to MCP servers and converts their tools into Semantic Kernel functions
- Includes a local .NET MCP server with 23 example tools (calculator, echo, file system, system info, text processing)
- Supports multiple MCP transports (Stdio by default; HTTP/HTTPS, WebSocket, Named Pipes are discussed but not implemented)
- Robust configuration with validation, retry logic, and structured logging via Serilog
- No Node.js required when using only the local server
Use cases of Integrating Model Context Protocol (MCP) Tools with Semantic Kernel: A Step-by-Step Guide
- Extend Semantic Kernel with external capabilities such as file system access or API calls
- Enable large language models to dynamically invoke tools based on user prompts
- Test and prototype MCP tool integration in a controlled local environment
- Build reusable AI agents that can interact with multiple data sources through a single protocol
FAQ from Integrating Model Context Protocol (MCP) Tools with Semantic Kernel: A Step-by-Step Guide
What is Model Context Protocol (MCP)?
MCP is an open-standard protocol for standardizing how applications provide context to AI models, acting as a universal connector between LLMs and diverse data sources like APIs, databases, or services.
Do I need Node.js and an OpenAI API key to run this demo?
No. Node.js is only required if you enable external MCP servers (GitHub, Everything). The OpenAI API key is needed only when integrating Semantic Kernel for function calling; the demo works without it using the local server.
How do I enable external MCP servers?
Edit src/Demo.MCP.Client/appsettings.json and change the "Enabled" property of the desired server from false to true. Restart the client. Do not replace the entire configuration objects.
What transport options does the demo support?
The demo currently uses Stdio transport for all servers (local, GitHub, Everything). Other transports like HTTP/HTTPS, WebSocket, and Named Pipes are described conceptually but not implemented.
Are there known limitations?
Tool names are case‑sensitive; parameters must be valid JSON. External servers require Node.js and internet access. The local server runs on the same machine and is managed as a subprocess by the client.
Frequently asked questions
What is Model Context Protocol (MCP)?
MCP is an open-standard protocol for standardizing how applications provide context to AI models, acting as a universal connector between LLMs and diverse data sources like APIs, databases, or services.
Do I need Node.js and an OpenAI API key to run this demo?
No. Node.js is only required if you enable external MCP servers (GitHub, Everything). The OpenAI API key is needed only when integrating Semantic Kernel for function calling; the demo works without it using the local server.
How do I enable external MCP servers?
Edit `src/Demo.MCP.Client/appsettings.json` and change the `"Enabled"` property of the desired server from `false` to `true`. Restart the client. Do not replace the entire configuration objects.
What transport options does the demo support?
The demo currently uses **Stdio** transport for all servers (local, GitHub, Everything). Other transports like HTTP/HTTPS, WebSocket, and Named Pipes are described conceptually but not implemented.
Are there known limitations?
Tool names are case‑sensitive; parameters must be valid JSON. External servers require Node.js and internet access. The local server runs on the same machine and is managed as a subprocess by the client.
Basic information
More Memory & Knowledge MCP servers
Mcp Knowledge Graph
shanehollomanMCP server enabling persistent memory for Claude through a local knowledge graph - fork focused on local development
Context Portal MCP (ConPort)
GreatScottyMacContext Portal (ConPort): A memory bank MCP server building a project-specific knowledge graph to supercharge AI assistants. Enables powerful Retrieval Augmented Generation (RAG) for context-aware development in your IDE.

PLUR
plur-aiAI agents start every session with amnesia — you re-explain the project, repeat your preferences, and correct the same mistakes over and over. PLUR gives them a memory that persists. Your agent's corrections, preference
Docs MCP Server
araboldGrounded Docs MCP Server: Open-Source Alternative to Context7, Nia, and Ref.Tools
Ultimate Google Docs & Drive MCP Server
a-bonusThe Ultimate Google Docs, Sheets, Drive, Gmail, & Google Calendar MCP Server. This MCP (primarily for use in Claude Desktop) gains full access to your google suite and lets claude do its thing.
Comments