Mcp Memory Bank

Created By
bsmi021a year ago
A powerful, production-ready context management system for Large Language Models (LLMs). Built with ChromaDB and modern embedding technologies, it provides persistent, project-specific memory capabilities that enhance your AI's understanding and response quality.
Overview

What is Mcp Memory Bank?

Mcp Memory Bank is a powerful context management system designed for Large Language Models (LLMs), utilizing ChromaDB and modern embedding technologies to provide persistent, project-specific memory capabilities that enhance AI understanding and response quality.

How to use Mcp Memory Bank?

To use Mcp Memory Bank, clone the repository, install the necessary dependencies, and run the application using Docker. A one-command setup is available for quick deployment.

Key features of Mcp Memory Bank?

  • High performance with optimized vector storage using ChromaDB
  • Project isolation with separate context spaces for different projects
  • Smart search capabilities, including semantic and keyword-based search
  • Real-time updates with dynamic content management
  • Precise recall through advanced embedding generation
  • Easy deployment with Docker support

Use cases of Mcp Memory Bank?

  1. Managing context for AI-driven applications
  2. Enhancing the performance of LLMs in specific projects
  3. Facilitating semantic and keyword searches in large datasets

FAQ from Mcp Memory Bank?

  • What technologies does Mcp Memory Bank use?

It is built with ChromaDB and modern embedding technologies.

  • Is Mcp Memory Bank suitable for production use?

Yes, it is designed to be production-ready with high performance and reliability.

  • How can I contribute to the project?

You can fork the repository, create a feature branch, and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bsmi021
Star
3
Language
TypeScript
License
MIT 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