Memory Bank MCP

Created By
tuncer-bytea year ago
Memory Bank is an MCP server that helps teams create, manage, and access structured project documentation. It generates and maintains a set of interconnected Markdown documents that capture different aspects of project knowledge, from high-level goals to technical details and day-to-day progress.
Overview

what is Memory Bank MCP?

Memory Bank MCP is a structured documentation system that helps teams create, manage, and access project knowledge through interconnected Markdown documents.

how to use Memory Bank MCP?

To use Memory Bank MCP, clone the repository, install dependencies, and configure the MCP settings. You can run it in development or production mode based on your needs.

key features of Memory Bank MCP?

  • AI-Generated Documentation using Gemini API
  • Structured Knowledge System with six core document types
  • MCP Integration for seamless AI assistant functionality
  • Customizable directory location for Memory Bank
  • Pre-defined Document Templates for various project aspects
  • AI-Assisted Updates for document management
  • Advanced Querying for context-aware document searches

use cases of Memory Bank MCP?

  1. Managing project documentation for software development teams.
  2. Creating structured knowledge bases for research projects.
  3. Facilitating collaboration and knowledge sharing among team members.

FAQ from Memory Bank MCP?

  • Can Memory Bank MCP integrate with other tools?

Yes! It is designed to work with AI assistants and can be integrated with various tools via the Model Context Protocol.

  • Is there a cost associated with using Memory Bank MCP?

Memory Bank MCP is open-source and free to use.

  • What types of documents can be created?

You can create project briefs, product contexts, system patterns, tech contexts, active contexts, and progress documents.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tuncer-byte
Star
24
Language
TypeScript
License
-
Tags

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