optimized-memory-mcp-server

Created By
AgentWonga year ago
Overview

What is Optimized Memory MCP Server?

The Optimized Memory MCP Server is a project designed to test and demonstrate Claude AI's coding abilities, focusing on effective AI workflows and prompt design. It implements a persistent memory system using a local knowledge graph, allowing Claude to remember user information across chats.

How to use Optimized Memory MCP Server?

To use the server, set it up with Docker or NPX, and configure it in your claude_desktop_config.json. You can then interact with the server through various API endpoints to manage entities and their relationships.

Key features of Optimized Memory MCP Server?

  • Persistent memory using a local knowledge graph
  • API for creating and managing entities and relations
  • Ability to add, delete, and search observations
  • Supports Docker and NPX for easy setup

Use cases of Optimized Memory MCP Server?

  1. Personalizing user interactions by remembering preferences and behaviors.
  2. Managing relationships and observations for enhanced AI conversations.
  3. Building a knowledge base for applications requiring user context.

FAQ from Optimized Memory MCP Server?

  • Can I use this server for any type of memory management?

Yes! The server is designed for flexible memory management across various applications.

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

No, you can create as many entities as needed, but performance may vary based on the size of the knowledge graph.

  • How do I retrieve information from the memory?

You can use the read_graph API to retrieve the entire knowledge graph or search_nodes to find specific entities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AgentWong
Star
-
Language
-
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)

18 minutes ago