Remember Me

Created By
phlaxa year ago
MCP server to persist chat artefacts and rules
Overview

What is Remember Me?

Remember Me is a persistence framework designed to maintain conversational context and rules in MCP-based language model applications. It allows for the storage and management of chat artifacts, including rules, snippets, and summaries.

How to use Remember Me?

To use Remember Me, install the package, run the MCP server, and connect it to your language model platform. You can then load contexts, manage rules, snippets, and summaries through the provided API.

Key features of Remember Me?

  • Persistent storage of chat artifacts and rules
  • Comprehensive API for context and resource management
  • Backup and restore functionality for context states

Use cases of Remember Me?

  1. Maintaining context in conversational AI applications
  2. Storing reusable code snippets for chatbots
  3. Preserving important summaries from user interactions

FAQ from Remember Me?

  • What types of resources can Remember Me store?

Remember Me can store rules, snippets, and summaries related to conversations.

  • Is Remember Me compatible with all language models?

Yes! Remember Me is designed to work with any MCP-based language model.

  • How do I back up my context?

You can create a backup using the my_context_backup_create() API call.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
phlax
Star
0
Language
Python
License
GPL-3.0 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