mcp-server-memory

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-server-memory?

The mcp-server-memory is a server designed to interact with a memory text file, enabling Claude and other MCP clients to manage memories during chat interactions.

how to use mcp-server-memory?

To use mcp-server-memory, you can utilize various commands such as memory_add, memory_search, memory_delete, and memory_list to manage memories effectively.

key features of mcp-server-memory?

  • Ability to append, search, delete, and list memories mid-chat.
  • Supports memory updates through a combination of delete and add commands.
  • Designed to enhance chat context by retaining relevant information across sessions.

use cases of mcp-server-memory?

  1. Storing user preferences and details for personalized responses.
  2. Managing context in ongoing conversations to improve interaction quality.
  3. Facilitating memory management for AI assistants in various applications.

FAQ from mcp-server-memory?

  • Can mcp-server-memory handle all types of memories?

Yes! It can manage various types of memories as long as they are formatted as strings.

  • Is there a limit to the number of memories?

Currently, there is no specified limit, but performance may vary based on the number of entries.

  • How does memory retrieval work?

Memories can be retrieved using the memory_search command, which matches substrings in the stored memories.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

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