optimized-memory-mcp-server

Created By
MCP-Mirrora year ago
Mirror of
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 good 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 to create entities, relations, and observations in the knowledge graph.

Key features of optimized-memory-mcp-server?

  • Persistent memory using a local knowledge graph
  • Ability to create and manage entities and their relationships
  • API for adding, deleting, and searching entities and observations
  • Integration with Claude AI for personalized interactions

Use cases of optimized-memory-mcp-server?

  1. Storing user preferences and behaviors for personalized AI interactions.
  2. Managing relationships between different entities in a knowledge graph.
  3. Enhancing AI's memory capabilities for better user experience.

FAQ from optimized-memory-mcp-server?

  • What programming language is used?

The server is implemented in Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License, allowing free use, modification, and distribution.

  • How can I build the server?

You can build it using Docker with the provided Dockerfile.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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