Memory Bank MCP Server

Created By
TerLand0bervera year ago
Overview

What is Memory Bank MCP Server?

Memory Bank MCP Server is a Model Context Protocol (MCP) server designed to manage project-specific memory bank data, utilizing an SQLite database to store and retrieve contextual information related to projects.

How to use Memory Bank MCP Server?

To use the Memory Bank MCP Server, you can run it directly using npx from the npm registry with the command: npx @telagod/memory-bank-mcp-server. Ensure you have Node.js version 18.0.0 or higher installed.

Key features of Memory Bank MCP Server?

  • Project-based memory management for each specified project path.
  • SQLite storage for structured and efficient data access.
  • Modular design encapsulating memory bank management logic.
  • Standardized interface with MCP tools for interaction.

Use cases of Memory Bank MCP Server?

  1. Managing project background information and decision logs.
  2. Tracking progress updates and milestones in development.
  3. Storing reusable patterns and design principles for knowledge retention.

FAQ from Memory Bank MCP Server?

  • Can I run this server on any platform?
    Yes, it can be run on Windows, macOS, and Linux, provided Node.js is correctly installed.

  • What is the database structure?
    The server uses SQLite with tables for product context, decisions, progress, focus, and system patterns to manage project data effectively.

  • Is there a way to integrate this server with other applications?
    Yes, it can be integrated into MCP-enabled applications like RooCode by configuring the mcp_settings.json file.

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

2 days ago