OKF Agent Memory — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track format and agent-tool compatibility as the memory specification evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Git-native repository memory using Open Knowledge Format

What we know

Pure-Go persistent memory for coding agents with BM25 search, progressive disclosure and an embedded stdio MCP server.

Maintenance / activity evidence

Observed Oct 4, 2026 (UTC)docs(release): reserve commits and tags for the maintainer and unify the

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Reads/writes knowledge bundle files. Writes: Create/update/relate concepts; Optional sync.
None locally; optional Hub token.
Sensitive access: Repository memory, Policy/decision data

Git storage improves provenance but can accidentally commit sensitive organizational knowledge if not scoped.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

723 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Does the current framework still expose the documented MCP or agent-memory integration?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Git storage improves provenance but can accidentally commit sensitive organizational knowledge if not scoped.
Reads/writes knowledge bundle files.
None locally; optional Hub token.
Local Git-native storage; optional encrypted/zero-knowledge Hub sync.
Reviewed write actions: Create/update/relate concepts; Optional sync
Sensitive access: Repository memory, Policy/decision data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Git-native memory files can be committed to the repository.
Optional Hub sync requires separate credentials.

Original activity observations

2026-10-04T20:17:56Z: docs(release): reserve commits and tags for the maintainer and unify the

Technical identity

github.com/okf-memory/okf-agent-memory

Exact implementation source: https://github.com/okf-memory/okf-agent-memory ↗
Reviewed resource type: MCP Server
Repository identity: okf-memory/okf-agent-memory

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
okf-memory/okf-agent-memory
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

claude-desktop

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
OKF Agent Memory provides Go CLI and embedded stdio MCP server for a project knowledge bundle.
Build/run the project’s Go `okf` CLI and register `okf mcp /ABSOLUTE/PATH/your-project/knowledge` in the MCP host. Not a publicly hosted account service.
Configure / authenticate
MCP100 setup guide
OKF Agent Memory is an agent-memory framework/repository with local Go binary and example MCP config; optional OKF Hub sync uses hub credentials.
Advanced configuration · claude desktop json · MCP100 composed guide
claude desktop json · MCP100 composed guide
{ "mcpServers": { "okf-memory": { "args": [ "mcp", "/ABSOLUTE/PATH/your-project/knowledge" ], "command": "/ABSOLUTE/PATH/okf-agent-memory/bin/okf" } } }
Check connection
Suggested check
Check local binary help or read-only memory query; no hub token required for default local mode.
Remove / uninstall / revoke
MCP100 setup guide
Only if exact server registered in Claude Code; preserve project knowledge folder and AGENTS.md instructions. Go binary can be deleted separately if originally built locally.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove okf-memory

Official Documentation & Sources

What it does

Pure-Go persistent memory for coding agents with BM25 search, progressive disclosure and an embedded stdio MCP server.

Capability: Files & Knowledge
Resource type: MCP Server
Industry: Software & Technology
Best fit: Git-native repository memory using Open Knowledge Format

Representative uses

Bootstrap repository memory
Search/show/create/update concepts
Relate concepts
Validate corpus

Limitations

Git-native memory files can be committed to the repository.
Optional Hub sync requires separate credentials.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: None locally; optional Hub token.
Permissions: Reads/writes knowledge bundle files.
Data handling: Local Git-native storage; optional encrypted/zero-knowledge Hub sync.
Cost: free
Risk and cautions: Git storage improves provenance but can accidentally commit sensitive organizational knowledge if not scoped.

Access scope and cautions

Write actions: Create/update/relate concepts Optional sync
Sensitive access: Repository memory Policy/decision data
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Bootstrap repository memory; Search/show/create/update concepts; Relate concepts; Validate corpus.

What setup and authentication are documented?

Recorded installation/entrypoint step: okf mcp knowledge. Recorded transport: stdio. Recorded environment-variable notes: OKF_HUB_TOKEN. No configuration values are supplied here. Prerequisites: okf binary. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local stdio keyless; optional Hub token for sync. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Create/update/relate concepts; Optional sync. Recorded permission boundary: Reads/writes knowledge bundle files.

What data-handling boundary should I consider?

Local Git-native storage; optional encrypted/zero-knowledge Hub sync. Recorded sensitive-access context: Repository memory; Policy/decision data.

What limitations and risks should I check before use?

Git storage improves provenance but can accidentally commit sensitive organizational knowledge if not scoped. Git-native memory files can be committed to the repository. Optional Hub sync requires separate credentials. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

OKF Memory is listed as Community implementation in MCP100’s current evidence.