ai-mlproductivity

Basic Memory

basicmachines-co

by basicmachines-co

Basic Memory is a knowledge management system that builds a persistent semantic graph in markdown, locally and securely.

Knowledge management system that builds a persistent semantic graph in markdown, locally.

github stars

2.6K

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Local-first storage in Markdown filesSemantic vector search with FastEmbedOptional cloud sync across devices

best for

  • / Researchers building persistent knowledge bases
  • / Writers organizing interconnected ideas and references
  • / Knowledge workers maintaining long-term project memory

capabilities

  • / Write and update markdown notes with semantic content
  • / Search notes by meaning using vector similarity and keywords
  • / Build context from previous conversations to continue discussions
  • / Create visual concept maps with Obsidian canvas
  • / Track recent activity across knowledge projects
  • / Read and manage file contents by path or permalink

what it does

A knowledge management system that lets LLMs build and query a persistent graph of interconnected notes stored as local Markdown files. Features semantic search and can visualize connections between concepts.

about

Basic Memory is an official MCP server published by basicmachines-co that provides AI assistants with tools and capabilities via the Model Context Protocol. Basic Memory is a knowledge management system that builds a persistent semantic graph in markdown, locally and securely. It is categorized under ai ml, productivity. This server exposes 17 tools that AI clients can invoke during conversations and coding sessions.

how to install

You can install Basic Memory in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

AGPL-3.0

Basic Memory is released under the AGPL-3.0 license.

readme

[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](https://www.gnu.org/licenses/agpl-3.0) [![PyPI version](https://badge.fury.io/py/basic-memory.svg)](https://badge.fury.io/py/basic-memory) [![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/) [![Tests](https://github.com/basicmachines-co/basic-memory/workflows/Tests/badge.svg)](https://github.com/basicmachines-co/basic-memory/actions) [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff) ![](https://badge.mcpx.dev?type=server 'MCP Server') ![](https://badge.mcpx.dev?type=dev 'MCP Dev') ## 🚀 Basic Memory Cloud is Live! - **Cross-device and multi-platform support is here.** Your knowledge graph now works on desktop, web, and mobile. - **Cloud is optional.** The local-first open-source workflow continues as always. - **OSS discount:** use code `BMFOSS` for 20% off for 3 months. [Sign up now →](https://basicmemory.com?utm_source=github&utm_medium=referral&utm_campaign=readme) with a 7 day free trial # Basic Memory Basic Memory lets you build persistent knowledge through natural conversations with Large Language Models (LLMs) like Claude, while keeping everything in simple Markdown files on your computer. It uses the Model Context Protocol (MCP) to enable any compatible LLM to read and write to your local knowledge base. ## What's New in v0.19.0 - **Semantic Vector Search** — find notes by meaning, not just keywords. Combines full-text and vector similarity for hybrid search with FastEmbed embeddings. - **Schema System** — infer, validate, and diff the structure of your knowledge base with `schema_infer`, `schema_validate`, and `schema_diff` tools. - **Per-Project Cloud Routing** — route individual projects through the cloud while others stay local, using API key authentication (`basic-memory project set-cloud`). - **FastMCP 3.0** — upgraded to FastMCP 3.0 with tool annotations for better client integration. - **CLI Overhaul** — JSON output mode (`--json`) for scripting, workspace-aware commands, and an htop-inspired project dashboard. - **Smarter Editing** — `edit_note` append/prepend auto-creates notes if they don't exist; `write_note` has an overwrite guard to prevent accidental data loss. - **Richer Search Results** — matched chunk text returned in search results for better context. See the full [CHANGELOG](CHANGELOG.md) for details. - Website: [basicmemory.com](https://basicmemory.com?utm_source=github&utm_medium=referral&utm_campaign=readme) - Documentation: [docs.basicmemory.com](https://docs.basicmemory.com?utm_source=github&utm_medium=referral&utm_campaign=readme) - Community: [Discord](https://discord.gg/tyvKNccgqN?utm_source=github&utm_medium=referral&utm_campaign=readme) ## Pick up your conversation right where you left off - AI assistants can load context from local files in a new conversation - Notes are saved locally as Markdown files in real time - No project knowledge or special prompting required https://github.com/user-attachments/assets/a55d8238-8dd0-454a-be4c-8860dbbd0ddc ## Quick Start ```bash # Install with uv (recommended) uv tool install basic-memory # Configure Claude Desktop (edit ~/Library/Application Support/Claude/claude_desktop_config.json) # Add this to your config: { "mcpServers": { "basic-memory": { "command": "uvx", "args": [ "basic-memory", "mcp" ] } } } # Now in Claude Desktop, you can: # - Write notes with "Create a note about coffee brewing methods" # - Read notes with "What do I know about pour over coffee?" # - Search with "Find information about Ethiopian beans" ``` You can view shared context via files in `~/basic-memory` (default directory location). ## Why Basic Memory? Most LLM interactions are ephemeral - you ask a question, get an answer, and everything is forgotten. Each conversation starts fresh, without the context or knowledge from previous ones. Current workarounds have limitations: - Chat histories capture conversations but aren't structured knowledge - RAG systems can query documents but don't let LLMs write back - Vector databases require complex setups and often live in the cloud - Knowledge graphs typically need specialized tools to maintain Basic Memory addresses these problems with a simple approach: structured Markdown files that both humans and LLMs can read and write to. The key advantages: - **Local-first:** All knowledge stays in files you control - **Bi-directional:** Both you and the LLM read and write to the same files - **Structured yet simple:** Uses familiar Markdown with semantic patterns - **Traversable knowledge graph:** LLMs can follow links between topics - **Standard formats:** Works with existing editors like Obsidian - **Lightweight infrastructure:** Just local files indexed in a local SQLite database With Basic Memory, you can: - Have conversations that build on previous knowledge - Create structured notes during natural conversations - Have conversations with LLMs that remember what you've discussed before - Navigate your knowledge graph semantically - Keep everything local and under your control - Use familiar tools like Obsidian to view and edit notes - Build a personal knowledge base that grows over time - Sync your knowledge to the cloud with bidirectional synchronization - Authenticate and manage cloud projects with subscription validation - Mount cloud storage for direct file access ## How It Works in Practice Let's say you're exploring coffee brewing methods and want to capture your knowledge. Here's how it works: 1. Start by chatting normally: ``` I've been experimenting with different coffee brewing methods. Key things I've learned: - Pour over gives more clarity in flavor than French press - Water temperature is critical - around 205°F seems best - Freshly ground beans make a huge difference ``` ... continue conversation. 2. Ask the LLM to help structure this knowledge: ``` "Let's write a note about coffee brewing methods." ``` LLM creates a new Markdown file on your system (which you can see instantly in Obsidian or your editor): ```markdown --- title: Coffee Brewing Methods permalink: coffee-brewing-methods tags: - coffee - brewing --- # Coffee Brewing Methods ## Observations - [method] Pour over provides more clarity and highlights subtle flavors - [technique] Water temperature at 205°F (96°C) extracts optimal compounds - [principle] Freshly ground beans preserve aromatics and flavor ## Relations - relates_to [[Coffee Bean Origins]] - requires [[Proper Grinding Technique]] - affects [[Flavor Extraction]] ``` The note embeds semantic content and links to other topics via simple Markdown formatting. 3. You see this file on your computer in real time in the current project directory (default `~/$HOME/basic-memory`). - Realtime sync can be enabled via running `basic-memory sync --watch` 4. In a chat with the LLM, you can reference a topic: ``` Look at `coffee-brewing-methods` for context about pour over coffee ``` The LLM can now build rich context from the knowledge graph. For example: ``` Following relation 'relates_to [[Coffee Bean Origins]]': - Found information about Ethiopian Yirgacheffe - Notes on Colombian beans' nutty profile - Altitude effects on bean characteristics Following relation 'requires [[Proper Grinding Technique]]': - Burr vs. blade grinder comparisons - Grind size recommendations for different methods - Impact of consistent particle size on extraction ``` Each related document can lead to more context, building a rich semantic understanding of your knowledge base. This creates a two-way flow where: - Humans write and edit Markdown files - LLMs read and write through the MCP protocol - Sync keeps everything consistent - All knowledge stays in local files. ## Technical Implementation Under the hood, Basic Memory: 1. Stores everything in Markdown files 2. Uses a SQLite database for searching and indexing 3. Extracts semantic meaning from simple Markdown patterns - Files become `Entity` objects - Each `Entity` can have `Observations`, or facts associated with it - `Relations` connect entities together to form the knowledge graph 4. Maintains the local knowledge graph derived from the files 5. Provides bidirectional synchronization between files and the knowledge graph 6. Implements the Model Context Protocol (MCP) for AI integration 7. Exposes tools that let AI assistants traverse and manipulate the knowledge graph 8. Uses memory:// URLs to reference entities across tools and conversations The file format is just Markdown with some simple markup: Each Markdown file has: ### Frontmatter ```markdown title: type: (e.g. note) permalink: - (such as tags) ``` ### Observations Observations are facts about a topic. They can be added by creating a Markdown list with a special format that can reference a `category`, `tags` using a "#" character, and an optional `context`. Observation Markdown format: ```markdown - [category] content #tag (optional context) ``` Examples of observations: ```markdown - [method] Pour over extracts more floral notes than French press - [tip] Grind size should be medium-fine for pour over #brewing - [preference] Ethiopian beans have bright, fruity flavors (especially from Yirgacheffe) - [fact] Lighter roasts generally contain more caffeine than dark roasts - [experiment] Tried 1:15 coffee-to-water ratio with good results - [resource] James Hoffman's V60 technique on YouTube is excellent - [question] Does water temperature affect extraction of different compounds differently? - [note] My favorite local shop uses a 30-second bloom time ``` ### Relations Relations are links to other topics. They define how entities ---

FAQ

What is the Basic Memory MCP server?
Basic Memory is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Basic Memory?
This profile displays 38 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.638 reviews
  • Ama Khanna· Dec 28, 2024

    We wired Basic Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Chaitanya Patil· Dec 8, 2024

    Basic Memory is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Piyush G· Nov 27, 2024

    Useful MCP listing: Basic Memory is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Noor Lopez· Nov 19, 2024

    Basic Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Shikha Mishra· Oct 18, 2024

    Basic Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Min Patel· Oct 10, 2024

    Useful MCP listing: Basic Memory is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Lucas Flores· Sep 13, 2024

    We wired Basic Memory into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Yash Thakker· Sep 9, 2024

    Basic Memory is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • James Chawla· Sep 1, 2024

    Basic Memory reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Dhruvi Jain· Aug 28, 2024

    We evaluated Basic Memory against two servers with overlapping tools; this profile had the clearer scope statement.

showing 1-10 of 38

1 / 4