mcpserver-semantickernel-client-demo

Created By
joslata year ago
Showing a super simple implementation of an c# MCP server hosted with Aspire and consumed by Semantic Kernel
Overview

what is mcpserver-semantickernel-client-demo?

This project demonstrates a simple implementation of a C# MCP (Microservices Communication Protocol) server hosted with Aspire and consumed by the Semantic Kernel.

how to use mcpserver-semantickernel-client-demo?

To use this demo, clone the repository from GitHub, set up the required environment, and run the server to see how it interacts with the Semantic Kernel.

key features of mcpserver-semantickernel-client-demo?

  • Simple implementation of an MCP server in C#.
  • Integration with the Semantic Kernel for enhanced functionality.
  • Easy to set up and run for demonstration purposes.

use cases of mcpserver-semantickernel-client-demo?

  1. Demonstrating the capabilities of the Semantic Kernel in a microservices architecture.
  2. Learning how to implement an MCP server in C#.
  3. Testing and developing applications that utilize the Semantic Kernel.

FAQ from mcpserver-semantickernel-client-demo?

  • What is the purpose of this demo?

The demo showcases how to implement a C# MCP server and its interaction with the Semantic Kernel.

  • Is this project suitable for production use?

This is a demo project and may require further development for production use.

  • Where can I find the source code?

The source code is available on GitHub at https://github.com/joslat/mcpserver-semantickernel-client-demo.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joslat
Star
0
Language
C#
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago