Mcp Server Demo

Created By
wazeerca year ago
Overview

what is Mcp Server Demo?

Mcp Server Demo is a demonstration project that showcases the capabilities of the C# MCP SDK, allowing developers to understand how to implement and utilize the Model Context Protocol in their applications.

how to use Mcp Server Demo?

To use the Mcp Server Demo, clone the repository from GitHub, set up the C# MCP SDK, and follow the instructions in the README file to run the demo server.

key features of Mcp Server Demo?

  • Demonstrates the implementation of the Model Context Protocol in C#.
  • Provides example code and usage scenarios for developers.
  • Easy to set up and run for testing purposes.

use cases of Mcp Server Demo?

  1. Learning how to integrate the Model Context Protocol in C# applications.
  2. Testing and experimenting with the MCP SDK functionalities.
  3. Serving as a reference for building production-level applications using MCP.

FAQ from Mcp Server Demo?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows for the management and interaction of data models in a structured way.

  • Is the Mcp Server Demo free to use?

Yes! The Mcp Server Demo is open-source and free to use for everyone.

  • Where can I find the documentation for the C# MCP SDK?

Documentation can be found in the GitHub repository of the C# MCP SDK.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wazeerc
Star
0
Language
C#
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago