
Neurakeep
io.github.dominiclachancePublished by GitHub account dominiclachancev0.1.0Updated Oct 24, 2026
Local-first, source-cited memory for AI agents with proposal review, failure memory, and MCP tools.
Overview
Gives AI assistants a local, source-cited memory vault they can search, read, and propose updates to, with human review before memory becomes durable.
- What you can do
- NeuraKeep is a local-first memory layer for MCP clients. It imports Markdown, text, JSONL, and PDFs into a local vault, preserves the raw sources, and extracts cited memory proposals. Tools such as memory_search, memory_read, memory_explain_sources, memory_propose_update, and memory_apply_update let an assistant search sources, facts, events, failures, and decisions, explain where a memory came from, and propose new memory. A graph view shows related memory with progressive expansion.
- When to use it
- Use it when several MCP clients should share one private memory store on your own machine and you want agent-proposed memories to be reviewed and traceable to sources before they become durable. It suits personal or small-team setups that prefer local storage over a hosted service.
- Requirements
- Runs locally over stdio as an npm package; needs Node.js 20+ and npm. The vault is initialized and served from a local root directory, and the CLI is invoked with node against the built dist/cli/index.js. No accounts, API keys, or environment variables are declared for local use. Hosted features such as SSO, team spaces, and billing are separate and not required locally.
Installation
In SourceWeft
- Open Neurakeep in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
NeuraKeep
NeuraKeep is a local-first memory system for AI agents.
It gives Claude Desktop, Claude Code, Codex, OpenClaw, Cursor-style tools, and other MCP clients a shared, source-cited memory layer that runs on your own machine.
What It Does
- Imports Markdown, text, JSONL, and PDFs into a local vault
- Preserves raw sources and extracts cited memory proposals
- Lets you review memory before it becomes durable
- Searches across sources, facts, events, failures, and decisions
- Organizes the local app into grouped Explore, Workflow, and System navigation
- Shows a Sigma knowledge graph with progressive expansion, clustering, search, keyboard access, and saved layouts
- Exposes MCP tools for agents:
memory_searchmemory_readmemory_explain_sourcesmemory_save(stores new text immediately and queues structured memory for review)memory_propose_updatememory_apply_update
The core rule is simple: agents can save new source memory immediately, but extracted durable facts remain reviewable and source-cited.
Local Install
Requirements:
- Node.js 22+
- npm
Open:
Start Free Locally
Use the local core when you want private, source-cited memory on your own machine:
- import Markdown, text, JSONL, or PDFs
- review extraction proposals before durable memory is applied
- connect Claude, Codex, OpenClaw, or another MCP client over stdio
Hosted NeuraKeep
Use the hosted app when you need Google or enterprise SAML/OIDC sign-in, private personal vaults, isolated shared Team spaces, remote MCP over HTTPS, managed storage, backups, and Stripe-managed billing. Team workspaces include owner/admin/reviewer/editor/viewer roles, email-bound invitations, audit history, licensed seats, and SCIM provisioning. Hosted access requires an active individual or Team subscription. OAuth-capable remote MCP clients use browser sign-in and explicit space consent with PKCE and rotating refresh tokens; space-bound, scoped, expiring manual grants remain available for non-interactive clients. Hosted autonomous spaces use application-level encryption at rest, but are not zero-knowledge because the authorized runtime decrypts them while working.
The public package contains the complete local-first core. Managed authentication, Stripe billing, Team tenancy, SSO, SCIM, deployment automation, and production credentials remain part of the hosted service and are not required to run NeuraKeep locally.
CLI Examples
Local MCP Setup
Example stdio MCP config:
Local HTTP mode:
Use --token or NEURAKEEP_MCP_TOKEN before exposing any HTTP endpoint outside your machine.
Free vs Paid
The open-source version is for local, self-managed memory. The hosted product adds managed auth, team spaces, remote connectors, shared storage, backups, and administration. See NeuraKeep pricing for the current hosted plans.
Docs
Development Checks
License
Apache-2.0
Source: README.md at commit 227a685
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.