Optimized Memory MCP Server v2

Created By
AgentWonga year ago
This is a personal project to test Claude AI's ability to self-write an MCP Server code for its own use.
Overview

What is Optimized Memory MCP Server v2?

Optimized Memory MCP Server v2 is a high-performance Python-based Model Context Protocol (MCP) server designed for Claude Desktop integration, focusing on efficient memory management and robust infrastructure component tracking.

How to use Optimized Memory MCP Server v2?

To use the server, clone the repository, set up the Python environment, install dependencies, configure the database, and start the server. Connect Claude Desktop to the server by setting the MCP server URL to http://localhost:8000.

Key features of Optimized Memory MCP Server v2?

  • Efficient memory management for large-scale infrastructure tracking
  • Comprehensive resource and tool implementations following MCP patterns
  • Full compatibility with Claude Desktop
  • SQLite-based persistent storage with connection pooling
  • Robust error handling and resource cleanup

Use cases of Optimized Memory MCP Server v2?

  1. Managing and tracking infrastructure components in real-time.
  2. Integrating with Claude Desktop for enhanced AI capabilities.
  3. Utilizing MCP resources for efficient entity management and observation tracking.

FAQ from Optimized Memory MCP Server v2?

  • Is this project still active?

No, the project has been archived due to faulty specifications and AI direction issues.

  • What are the system requirements?

Requires Python 3.13.1 or higher and SQLite 3.x.

  • How can I contribute to the project?

You can fork the repository, create a feature branch, and submit a pull request after making your changes.

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