model-context-protocol

Created By
PyBhagyaa year ago
A custom server project built using the Model Context Protocol (MCP) in Python. This repository documents my learning, experiments, and development progress.
Overview

What is Model Context Protocol?

Model Context Protocol (MCP) is a custom server project built in Python that implements an AI Sticky Notes application, showcasing the core functionalities of the MCP framework.

How to use Model Context Protocol?

To use the MCP server, clone the repository and run the server using the command python main.py. You can then interact with the API to manage notes.

Key features of Model Context Protocol?

  • Adding new notes to persistent storage
  • Retrieving all stored notes
  • Accessing the most recent note
  • Generating AI summaries of notes

Use cases of Model Context Protocol?

  1. Developers can extend functionality by adding new tools and resources.
  2. Users can manage their notes and get AI-generated summaries.
  3. It serves as a reference for structuring MCP applications.

FAQ from Model Context Protocol?

  • Can I add new features to the MCP server?

Yes! The server is designed to be extensible, allowing you to add new tools and resources.

  • How do I run the server?

Simply clone the repository and execute python main.py to start the server.

  • Is there a way to categorize notes?

Future enhancements may include note categorization and tagging.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PyBhagya
Star
0
Language
Python
License
Unlicense license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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