Build your MCP Server using C# SDK

Created By
aarthiema year ago
Build MCP server
Overview

what is MCPServerTest?

MCPServerTest is a project designed to help users build their own Model Context Protocol (MCP) server using the C# SDK. It serves as an educational resource for developers interested in understanding and implementing MCP servers.

how to use MCPServerTest?

To use MCPServerTest, follow these steps: 1. Create a .NET console application. 2. Add the necessary NuGet packages. 3. Decorate your methods with the appropriate attributes to expose them as MCP tools. 4. Build the project and configure the server settings. 5. Run your server and interact with it using GitHub Copilot Chat.

key features of MCPServerTest?

  • Simple setup for creating an MCP server using C#.
  • Includes methods for echoing, reversing, and calculating the length of input strings.
  • Integration with GitHub Copilot for enhanced interaction.

use cases of MCPServerTest?

  1. Building custom MCP servers for various applications.
  2. Learning how to implement server-side logic in C#.
  3. Experimenting with AI tools like GitHub Copilot in a server environment.

FAQ from MCPServerTest?

  • What is the purpose of this project?

This project is for educational purposes to explore building MCP servers using C# SDK.

  • Is there any cost associated with using MCPServerTest?

No, it is free to use for educational purposes.

  • Can I extend the functionality of the MCP server?

Yes, you can add more methods and features as needed.

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