MyFirstMCP - Model Context Protocol Server Example

Created By
iamgauravna year ago
This is a simple C# implementation of a Model Context Protocol (MCP) server using .NET 9. The project demonstrates how to create an MCP server with basic functionality including monkey and selling services.
Overview

what is MyFirstMCP?

MyFirstMCP is a simple C# implementation of a Model Context Protocol (MCP) server using .NET 9, designed to demonstrate the creation of an MCP server with basic functionalities including monkey and selling services.

how to use MyFirstMCP?

To use MyFirstMCP, clone the repository, open the project in Visual Studio Code, restore NuGet packages, and run the project with the provided configuration.

key features of MyFirstMCP?

  • MonkeyService: Fetches monkey data from an external API.
  • SellingService: Manages selling records.
  • MCP Tools: Provides command interfaces for the services.

use cases of MyFirstMCP?

  1. Fetching and displaying monkey data for educational purposes.
  2. Managing and recording sales transactions in applications.
  3. Serving as a backend for applications that require context-based data management.

FAQ from MyFirstMCP?

  • What are the prerequisites for running MyFirstMCP?

You need .NET 9.0 SDK and Visual Studio Code or Visual Studio 2022.

  • How do I configure the MCP server?

You need to add the specified configuration to your claude_desktop_config.json file, ensuring the project path matches your local environment.

  • Is there any documentation available?

Yes, references for building an MCP server in C# and a quick start guide are provided in the project.

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