MCP Notes Server

Created By
truaxkia year ago
A Model Context Protocol (MCP) server implementation providing persistent note management created with Python SDK.
Overview

what is MCP Notes Server?

MCP Notes Server is a Model Context Protocol (MCP) server implementation designed for managing notes with persistent storage, built using Python SDK.

how to use MCP Notes Server?

To use MCP Notes Server, install it via Smithery or manually set it up by creating a virtual environment and installing the required dependencies. Start the server and use the provided tools to manage your notes.

key features of MCP Notes Server?

  • Create, read, update, and delete notes
  • Persistent storage using JSON
  • Timestamp tracking for creation and modifications
  • Note summarization via prompts
  • Resource-based access using note:// URI scheme

use cases of MCP Notes Server?

  1. Managing personal notes with easy access and modification.
  2. Collaborative note-taking for teams using the server.
  3. Summarizing notes for quick reviews and insights.

FAQ from MCP Notes Server?

  • Can I access my notes from different devices?

Yes! As long as the server is running, you can access your notes from any device connected to it.

  • Is there a limit to the number of notes I can create?

No, you can create as many notes as your storage allows.

  • How does the note summarization feature work?

The server uses prompts to generate summaries of your notes, which can be brief or detailed based on your needs.

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