Simple MCP Server Example

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Simple MCP Server Example?

This project is a basic implementation of a Model Context Protocol (MCP) server using FastAPI, designed to demonstrate the core concepts of MCP by providing a simple context service.

how to use Simple MCP Server Example?

To use the server, first install the required dependencies and then run the server using Uvicorn. You can interact with the server through its endpoints.

key features of Simple MCP Server Example?

  • Basic health check endpoint
  • Context endpoint that processes prompt templates
  • Support for parameterized prompts

use cases of Simple MCP Server Example?

  1. Providing context for various prompts in applications.
  2. Health monitoring of the server.
  3. Demonstrating the functionality of MCP in a simple setup.

FAQ from Simple MCP Server Example?

  • What is the purpose of the health check endpoint?

The health check endpoint is used to verify that the server is running and responsive.

  • How can I send a request to the context endpoint?

You can send a POST request to the /context endpoint with the required parameters in JSON format.

  • Is this server suitable for production use?

This example is primarily for educational purposes and may require additional features and security measures for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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)

2 days ago