MCP Server Memos

Created By
ChenyqThua year ago
Overview

What is MCP Server Memos?

MCP Server Memos is a server designed to interact with the Memos note-taking service using the MCP protocol, allowing users to manage their notes through natural language commands.

How to use MCP Server Memos?

To use MCP Server Memos, you need to configure the server with your Memos URL and access token, then run the server and interact with it through supported clients.

Key features of MCP Server Memos?

  • 🔍 Search notes
  • ✨ Create new notes with visibility settings
  • 📖 Retrieve note content
  • ✏️ Update existing notes
  • 🔐 Secure authentication using access tokens

Use cases of MCP Server Memos?

  1. Quickly searching for notes using keywords.
  2. Creating and managing notes through voice or text commands.
  3. Updating notes on-the-fly during meetings or brainstorming sessions.

FAQ from MCP Server Memos?

  • Can I use MCP Server Memos with any client?

Yes! As long as the client supports the MCP protocol, you can use it with MCP Server Memos.

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

No, you can create as many notes as your Memos server allows.

  • How do I secure my access token?

It is recommended to use environment variables for sensitive information instead of command-line parameters.

Server Config

{
  "mcpServers": {
    "mcp-server-memos": {
      "command": "npx",
      "args": [
        "-y",
        "@chenyqthu/mcp-server-memos"
      ],
      "env": {
        "MEMOS_URL": "https://your-memos-server",
        "MEMOS_TOKEN": "your_access_token"
      }
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
ChenyqThu
Star
0
Language
JavaScript
License
-
Category
note-taking
Tags

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