MCP-Memos

Created By
huhu415a year ago
A memo tool based on MCP protocol that helps developers quickly save and retrieve text information without interrupting their workflow.
Overview

what is MCP-Memos?

MCP-Memos is a memo tool based on the MCP protocol that helps developers quickly save and retrieve text information without interrupting their workflow.

how to use MCP-Memos?

To use MCP-Memos, download the binary file, configure it in the macPilotCli configuration file, and use voice commands to record and retrieve information.

key features of MCP-Memos?

  • Quick saving of text information without switching applications
  • Easy retrieval of saved information using keywords or tags
  • Voice command functionality for recording and retrieving memos

use cases of MCP-Memos?

  1. Developers needing to record quick notes during coding sessions.
  2. Teams wanting to share and retrieve important information without disrupting their workflow.
  3. Individuals looking for a seamless way to manage text information on the go.

FAQ from MCP-Memos?

  • Can MCP-Memos be used on any operating system?

Yes! MCP-Memos can be installed on any system that supports the binary file.

  • Is there a limit to how much I can save?

No, you can save as much information as you need, as long as you manage your storage effectively.

  • How do I retrieve my saved memos?

Simply use the voice command to ask for the records based on the description you provided when saving.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
huhu415
Star
0
Language
Go
License
-
Category
note-taking

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)

a day ago