Skip to main content
mcpSource-backed
Basic Memory logo

Basic Memory MCP Server

Local-first Basic Memory MCP server for giving Claude a persistent Markdown knowledge base with note editing, semantic search, recent activity, knowledge graph context, projects, schema tools, and optional cloud sync.

by Basic Machines · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://docs.basicmemory.com, https://github.com/basicmachines-co/basic-memory, https://basicmemory.com
Brand
Basic Memory
Brand domain
basicmemory.com
Brand asset source
brandfetch
Safety notes
Basic Memory MCP can create, edit, move, and delete notes in the configured project., The server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools., Edit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth., Imports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base., Auto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv., The optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication.
Privacy notes
Local notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research., Cloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine., The README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking., Logs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes., Keep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files.
Author
Basic Machines
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime1Network & hosting1Review & approval1General210 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens.

4 areas
  • SafetyGeneralBasic Memory MCP can create, edit, move, and delete notes in the configured project.
  • SafetyGeneralThe server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools.
  • SafetyGeneralEdit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth.
  • SafetyGeneralImports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base.
  • SafetyExecution & processesAuto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv.
  • SafetyGeneralThe optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication.
  • PrivacyCredentials & tokensLocal notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research.
  • PrivacyGeneralCloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine.
  • PrivacyLocal filesThe README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking.
  • PrivacyLocal filesLogs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes.
  • PrivacyCredentials & tokensKeep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files.

Safety notes

  • Basic Memory MCP can create, edit, move, and delete notes in the configured project.
  • The server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools.
  • Edit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth.
  • Imports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base.
  • Auto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv.
  • The optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication.

Privacy notes

  • Local notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research.
  • Cloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine.
  • The README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking.
  • Logs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes.
  • Keep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files.

Prerequisites

  • Python 3.12 or newer available through uv for the local MCP server.
  • A selected Basic Memory project directory for Markdown notes and generated metadata.
  • Backups or version control for important notes before enabling model-assisted writes.
  • Team agreement on whether notes stay local, sync through the optional cloud service, or route per project.
  • Review of telemetry, promo, logging, and cloud settings before using the server with sensitive work.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "basic-memory": {
      "command": "uvx",
      "args": ["basic-memory", "mcp"]
    }
  }
}

About this resource

Content

Basic Memory MCP Server gives Claude and other MCP clients a persistent knowledge base built from Markdown files. It combines note writing, editing, semantic search, recent activity, wikilinks, observations, and knowledge graph context so conversations can continue from project memory instead of restarting from scratch.

The project is local-first and AGPL-licensed, with an optional paid cloud path for hosted sync, team workspaces, snapshots, and cross-device access. The same repository also includes host-native packages such as a Claude Code plugin and shared skills, but this entry is scoped to the MCP server exposed by uvx basic-memory mcp.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live website, documentation, repository, MCP metadata, PyPI metadata, and license for current install commands, supported clients, tool lists, cloud behavior, telemetry controls, and licensing.

Features

  • Local-first Markdown notes that humans and Claude can both read and write.
  • Stdio setup with uvx basic-memory mcp.
  • Claude Desktop, Claude Code, Codex, Cursor, VS Code, ChatGPT, Obsidian, and generic MCP-client guidance.
  • Content tools including write_note, read_note, edit_note, move_note, delete_note, read_content, and view_note.
  • Search and discovery tools including search, search_notes, recent_activity, and list_directory.
  • Knowledge graph tools including build_context and Obsidian canvas generation.
  • Project tools for listing, creating, selecting, routing, and checking sync status.
  • Schema tools for inferring, validating, and diffing knowledge-base structure.
  • Optional cloud tools and per-project cloud routing.
  • Semantic search with full-text and vector ranking.
  • Tool annotations for read-only, destructive, idempotent, and open-world behavior hints.

Installation

For Claude Code, the README documents:

claude mcp add basic-memory -- uvx basic-memory mcp

For MCP clients that use JSON configuration:

{
  "mcpServers": {
    "basic-memory": {
      "command": "uvx",
      "args": ["basic-memory", "mcp"]
    }
  }
}

After connecting, choose the project that should hold the Markdown notes and verify that Claude can search existing notes before allowing write operations.

Use Cases

  • Ask Claude to create a note for an architecture decision, incident finding, or research summary.
  • Search project memory before starting a new implementation task.
  • Build context around a note or relation before continuing a conversation.
  • Track recent activity across project notes.
  • Keep Obsidian-readable Markdown in sync with agent-authored notes.
  • Import old Claude or ChatGPT conversations into a searchable knowledge base.
  • Validate the inferred schema of a shared project memory space.
  • Route selected projects through the cloud while keeping others local.
  • Pair Basic Memory's MCP server with its Claude Code plugin for session briefings and checkpoint workflows.

Safety and Privacy

Basic Memory is a memory system, so its main risk is durable context. Notes can outlive a single conversation, be searched later, and be synced to other devices or teammates. Review proposed writes, edits, moves, deletes, imports, schema changes, and cloud-routing changes before allowing Claude to apply them.

Keep sensitive credentials, customer records, private project paths, regulated data, and imported conversation archives out of notes unless the local storage, sync path, retention policy, and model provider are approved for that data. Back up important Markdown before model-assisted cleanup or schema work, and review telemetry, log level, promo, and cloud settings for sensitive projects.

Disclosure

Basic Memory offers both an open-source local MCP server and an optional paid cloud service. This listing is not sponsored, paid, or affiliate-driven, and it is scoped to the source-backed MCP server.

Duplicate Check

No Basic Memory, basicmachines-co/basic-memory, or basic-memory mcp entry was found in content/mcp, content/tools, content/guides, content/agents, or content/skills.

Source citations

Add this badge to your README

Show that Basic Memory MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/basic-memory-mcp-server.svg)](https://heyclau.de/entry/mcp/basic-memory-mcp-server)

How it compares

Basic Memory MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Local-first Basic Memory MCP server for giving Claude a persistent Markdown knowledge base with note editing, semantic search, recent activity, knowledge graph context, projects, schema tools, and optional cloud sync.

Open dossier

MCP server for semantic codebase intelligence, combining AST structure, embeddings, clustering, feature hubs, restore points, and memory graph tools.

Open dossier

Official reference MCP server that gives Claude persistent memory through a local knowledge graph of entities, relations, and observations, stored in a file on your own machine.

Open dossier

Remote Agentage Memory MCP server giving Claude one shared, portable memory across every AI you use - search, read, write, edit, list, and delete plain Markdown notes you own, over Streamable HTTP with OAuth 2.1.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1glorydavid03023vreshch
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandBasic Memory logoBasic MemoryAgentage Memory logoAgentage Memory
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorBasic MachinesforloopcodesModel Context Protocolagentage
Added2026-06-062026-06-052026-06-032026-06-18
Platforms
Harness
Source repo
Safety notesBasic Memory MCP can create, edit, move, and delete notes in the configured project. The server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools. Edit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth. Imports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base. Auto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv. The optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication.Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes. The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving. Static analysis tools may invoke local compilers, linters, or language tools depending on the repository. Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends. External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context.Persists remembered information to a local file on disk (its location can be set with MEMORY_FILE_PATH); manage and review that file as it accumulates data. Runs locally as an stdio process and makes no external network calls; the knowledge graph stays on your machine.The memory__write, memory__edit, and memory__delete tools create, modify, and remove your stored notes; review actions before granting broad access.
Privacy notesLocal notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research. Cloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine. The README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking. Logs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes. Keep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files.Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider. Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans. Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts. Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts.Details Claude chooses to remember are written to and read from the local memory file, so it can retain personal or project information across sessions. Review or clear the memory file if it should not retain sensitive data, and use MEMORY_FILE_PATH to control where it is stored.Notes you read or write are stored server-side in your Agentage Memory and mirrored locally as Markdown you can export anytime; note contents pass through model context.
Prerequisites
  • Python 3.12 or newer available through uv for the local MCP server.
  • A selected Basic Memory project directory for Markdown notes and generated metadata.
  • Backups or version control for important notes before enabling model-assisted writes.
  • Team agreement on whether notes stay local, sync through the optional cloud service, or route per project.
  • Node.js and npx available to the MCP client runtime.
  • A repository or workspace you are authorized to index and expose to an MCP client.
  • Ollama embedding model available, or an approved OpenAI-compatible embedding provider and API key.
  • Static analysis tools installed if you want Context+ to run native linters or compilers.
  • Node.js 18+ and npx available (verify with: npx --version)
  • Claude Code or Claude Desktop with MCP support
  • A writable location for the memory file, optionally set with the MEMORY_FILE_PATH environment variable
  • agentage account (sign in at memory.agentage.io)
  • OAuth 2.1 authentication (PKCE + Dynamic Client Registration, handled in the connect flow)
  • Network access to memory.agentage.io (HTTPS required)
  • Claude Desktop 0.7.0+ or Claude Code with MCP (HTTP transport) support
Install
claude mcp add basic-memory -- uvx basic-memory mcp
npx -y contextplus
claude mcp add memory -- npx -y @modelcontextprotocol/server-memory
claude mcp add --transport http agentage-memory https://memory.agentage.io/mcp && claude mcp list
Config
{
  "mcpServers": {
    "basic-memory": {
      "command": "uvx",
      "args": ["basic-memory", "mcp"]
    }
  }
}
{
  "mcpServers": {
    "contextplus": {
      "command": "npx",
      "args": ["-y", "contextplus"],
      "env": {
        "CONTEXTPLUS_EMBED_PROVIDER": "ollama",
        "OLLAMA_EMBED_MODEL": "nomic-embed-text",
        "OLLAMA_CHAT_MODEL": "llama3.2"
      }
    }
  }
}
{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "agentage-memory": {
      "url": "https://memory.agentage.io/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.