MCP.Market

okl — Observed Knowledge Ledger MCP server

by emeraldleaf·io.github.emeraldleaf/okl·v0.13.0

Keeps your agent true to your rules. Keeps them true to the code. Keeps learning as you build.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars659 downloads/wk

Reviews

Write one

Nobody has reviewed okl — Observed Knowledge Ledger yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

okl — Observed Knowledge Ledger tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How okl — Observed Knowledge Ledger compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 4,460 AI and agents servers
Downloads a week
659
more than 90% of 1,538 AI and agents servers with a package

Release history: 9 versions in the registry since 2026-10-03, latest 2026-11-03, typically one every 3 days.

Install okl — Observed Knowledge Ledger in Claude Code, Cursor or VS Code

claude mcp add okl -- uvx observed-knowledge-ledger
Add to Cursor

What the publisher says

From the okl — Observed Knowledge Ledger repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.emeraldleaf/okl -->

okl — Observed Knowledge Ledger

A learning loop that keeps coding agents — and your docs — from drifting. Engineering rules, architecture decisions, documentation and diagrams: recorded once, briefed to Claude Code or any MCP agent before every task, proven by checks, and flagged in CI when what they govern changes. Use it in one repo, or share one store across every repo your team runs.

🚀 Quickstart · 📘 Getting started guide · 🔬 How it works · 📊 Results · 🧪 Eval report · 🧩 Plugin

A small store of what a codebase knows — its conventions, architecture decisions and

why they were made, the checks that catch mistakes already made once, and the claims its

docs and diagrams make — plus a hook that hands the relevant ones to a coding agent (or a

person) before they start a task. Each session can record what it learned, so the store

grows with the work; it survives past a session and can be shared across a team. And it

stays true: an entry is verified by running a check, and flagged when the files it governs

change, whether those are code, docs or diagrams.

Quickstart

New here? docs/GETTING-STARTED.md walks through setup, the

habit of adding to the canon as you build a feature, and keeping your docs from drifting.

1. Install the CLI (the PyPI name differs — PyPI refuses okl as confusable with oki — but everything you type afterwards is okl):

pipx install 'observed-knowledge-ledger[mcp]'

Needs Python 3.10+ (and git for drift detection). Tested on macOS and Linux. Windows is untested: the core should work, but the Claude Code hooks likely need fixes there (#85).

2. Wire your repo. From the repository root:

okl init --repo my-repo --dry-run   # lists every file it would write; writes nothing
okl init --repo my-repo             # config, Claude Code hooks, MCP server, CI workflow, starter lessons

init detects your stack (*.csproj, package.json, pyproject.toml …), sets the repo's interests from it, and fills the store with 20 starter lessons that hold on almost any codebase plus the bundled packs for your stack, so the first prompt is already briefed (--interests chooses your own subjects; --no-seed leaves the store empty).

init wires Claude Code when the repo has a .claude/ directory or claude is on your PATH; --claude forces it and --no-claude skips it. Prefer the plugin? Install it before running init — /plugin marketplace add emeraldleaf/okl, then /plugin install okl@okl in Claude Code — and init leaves the hooks to the plugin, so nothing is wired twice. (Installed after? okl doctor reports the double wiring, and okl init --uninstall removes the project copy.)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

okl — Observed Knowledge Ledger: common questions

Is okl — Observed Knowledge Ledger MCP server safe?
Mostly: it is graded B (77/100). Read the okl — Observed Knowledge Ledger safety report
How do I install okl — Observed Knowledge Ledger?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does okl — Observed Knowledge Ledger need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is okl — Observed Knowledge Ledger maintained?
The last commit was 32 days ago (2026-10-03). The latest release is v0.13.0.
What can I use instead of okl — Observed Knowledge Ledger?
Servers from other publishers that do the same job: Roast My Design System MCP server, Roast My Design System MCP server and Basic Memory MCP server.
How does okl — Observed Knowledge Ledger compare with other AI and agents MCP servers?
safety score 77/100 (higher than 50% of 4,460 AI and agents servers); downloads a week 659 (more than 90% of 1,538 AI and agents servers with a package). Full comparison.

Alternatives to okl — Observed Knowledge Ledger

Same job from other publishers: the closest match first, then the best rated.

  • Roast My Design System
    Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
    A
  • Roast My Design System
    Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
    A
  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • IWE (iwe.md)
    Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
    A
  • SuperCompress
    Compress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex.
    B