Evermemos Mcp

Created By
tt-a1i3 months ago
Universal long-term memory layer for AI coding assistants. 7 MCP tools for remember, recall, briefing, forget with sensitive content guard, memory conflict detection, and space isolation. Powered by EverMemOS.
Overview

What it does

evermemos-mcp gives AI coding assistants (Claude Code, Cursor, Cline, Cherry Studio) persistent cross-session memory via EverMemOS Cloud.

Key Features

  • 7 MCP tools: list_spaces, remember, request_status, recall, briefing, forget, fetch_history
  • Space isolation: coding:my-app, chat:preferences, study:ml-notes — memories never bleed across projects
  • Sensitive content guard: Detects API keys, passwords, tokens before storing — blocks and asks user to confirm
  • Memory conflict detection: Auto-checks for similar memories in chat spaces, surfaces conflicts for the agent to decide
  • 6 retrieval strategies: keyword, hybrid, vector, RRF, agentic, auto
  • Lifecycle tracking: queued → provisional → fallback → searchable across all tools
  • Benchmark: 60/60 recall success vs 0/60 baseline, zero attribution errors, P95 < 2s

Quick Start

uvx evermemos-mcp@latest

Get your API key at https://evermind.ai/

Server Config

{
  "mcpServers": {
    "evermemos-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "evermemos-mcp@latest"
      ],
      "env": {
        "EVERMEMOS_API_KEY": "<YOUR_API_KEY>",
        "EVERMEMOS_USER_ID": "mcp-user"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
tt-a1i
Star
-
Language
-
License
-
Category

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