MCP Server Memos 📝

Created By
RyoJerryYua year ago
A Python package enabling LLM models to interact with the Memos server via the MCP interface for searching, creating, retrieving, and managing memos.
Overview

What is MCP Server Memos?

MCP Server Memos is a Python package that allows LLM models to interact with the Memos server through the MCP (Model Context Protocol) interface for searching, creating, retrieving, and managing memos.

How to use MCP Server Memos?

To use this package, include it in your configuration file as a plugin, or install it via pip or Smithery. You can also run it as a command line tool or as a library in your Python code.

Key features of MCP Server Memos?

  • 🔍 Search memos with keywords
  • ✨ Create new memos with customizable visibility
  • 📖 Retrieve memo content by ID
  • 🏷️ List and manage memo tags
  • 🔐 Secure authentication using access tokens

Use cases of MCP Server Memos?

  1. Automating memo management in applications.
  2. Integrating memo functionalities into LLM-based systems.
  3. Enhancing productivity tools with memo capabilities.

FAQ from MCP Server Memos?

  • Can I use MCP Server Memos with any LLM model?

Yes! It is designed to work with various LLM models that support the MCP interface.

  • Is there a cost associated with using MCP Server Memos?

No, it is open-source and free to use under the MIT License.

  • How do I authenticate with the Memos server?

You need to provide an access token in your configuration to authenticate.

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