sk-mcp-sample

Created By
vtjc2002a year ago
Semantic Kernel with MCP server/client sample using SSE transport protocal
Overview

What is sk-mcp-sample?

sk-mcp-sample is a sample project demonstrating the use of Semantic Kernel with a server/client architecture utilizing the SSE (Server-Sent Events) transport protocol.

How to use sk-mcp-sample?

To use sk-mcp-sample, clone the repository from GitHub, set up the server and client as per the instructions in the README, and run the application to see the SSE communication in action.

Key features of sk-mcp-sample?

  • Demonstrates the integration of Semantic Kernel with MCP (Multi-Channel Protocol).
  • Utilizes SSE for real-time data streaming between server and client.
  • Provides a clear example for developers to understand server/client communication.

Use cases of sk-mcp-sample?

  1. Learning how to implement server/client architecture using SSE.
  2. Understanding the integration of Semantic Kernel in applications.
  3. Developing real-time applications that require efficient data streaming.

FAQ from sk-mcp-sample?

  • What programming language is used in this project?

The project is developed in C#.

  • Is there any documentation available?

Yes, documentation is available in the GitHub repository.

  • Can I contribute to this project?

Yes, contributions are welcome! Please follow the guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vtjc2002
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