okf-mcp 0.8.0

Full Changelog: v0.7.0...v0.8.0

okf-mcp 0.7.0

Highlights

• Adds read-only okf_validate_changes and a fully described create/update batch contract.
• Returns target, semantic-effect, validation, Git, and durability receipts with immediate reindexing.
• Derives ergonomic paths from strong catalog conventions and improves Git-source size diagnostics.
• Adds exact automatic commits built from validated bytes with isolated-tree construction, pinned-branch CAS publication, and race-safe Git index synchronization.
• Protects generated concepts, computation contracts, hidden/control paths, filters, fsmonitor helpers, replace refs, hidden index flags, and concurrent writers.

Validated by 169 tests, self-validation, package dry-run, installed-tarball MCP smoke in both protocol eras, and fake/Xingu agent workflows.

okf-mcp 0.6.0

Full Changelog: v0.5.1...v0.6.0

okf-mcp 0.5.1

What changed

• Replace substring ranking with process-local MiniSearch BM25+ retrieval.
• Require all case-insensitive query terms while preserving structured filters, exact totals, pagination, and deterministic ordering.
• Add bounded query contracts, MCP/CLI coverage, cache-rebuild tests, and a reusable local search benchmark.
• Document retrieval behavior and validate the release against the Xingu OKF catalog.

Validation

• 132 tests passed.
• OKF self-validation passed.
• Packed-package MCP smoke passed in modern and legacy protocol modes.
• Xingu OKF validation passed with zero diagnostics.

okf-mcp 0.5.0

Summary

okf-mcp 0.5.0 replaces the custom MCP/JSON-RPC transport with the official Model Context Protocol TypeScript SDK v2 while preserving the v0.2 catalog, graph, migration, Git-source, and review-only authoring behavior introduced in 0.4.0.

Highlights

• Serves the modern MCP 2026-07-28 revision and the SDK compatibility path for 2025-era clients, including 2025-11-25.
• Uses SDK-native stdio framing, negotiation, resource templates, tool dispatch, and JSON Schema validation.
• Removes the custom protocol dispatcher and validator.
• Preserves capability-gated tools, serialized mutations, eager catalog loading, bounded input, and masked internal errors.
• Canonicalizes resource URIs so paths containing spaces work through standard clients.
• Tests all MCP integration behavior through the official client SDK, including clean-installed package smoke tests in both protocol eras.

Compatibility

The CLI, stdio command, tools, resources, OKF v0.2 behavior, v0.1 migration support, and optional project mode remain available. The undocumented programmatic createServer().handle(...) dispatcher has been removed; embedded consumers should use createMcpServer() or runStdioServer().

Verification

• 128 tests passed locally and in GitHub CI on Node 22 and Node 24.
• The bundled OKF reference is conformant and project-valid.
• Clean tarball installation and real stdio MCP sessions passed in modern and legacy modes.
• The external xingu-okf v0.2 catalog passed with 451 documents, 420 concepts, 3,659 edges, and no broken links or relations.
• Its pinned Kiliagon Suite Git-source reference resolved from the declared commit through MCP.
• Production dependency audit reported no vulnerabilities.

okf-mcp 0.4.0

Summary

okf-mcp 0.4.0 adds root-first Open Knowledge Format v0.2 support while preserving the existing optional workspace and multi-bundle interfaces.

Highlights

• Supports the official v0.2 provenance, trust, lifecycle, resource, and Attested Computation fields with CommonMark-aware parsing.
• Uses portable, extensionless Concept IDs in single-root mode; okf:// remains an optional okf-mcp workspace locator.
• Indexes explicitly referenced inert assets and pinned Git sources without executing or implicitly fetching referenced code.
• Adds static Attested Computation inspection, digest preparation, and separately gated proposal authoring. It never executes computation or claims attestation.
• Preserves the v0.1 timestamp and # Citations read fallbacks and adds a conservative, review-only v0.2 migration workflow and packaged Codex skill.
• Hardens proposal acceptance, local path boundaries, immutable remote loading, graph validation, and MCP/CLI parity.

Compatibility

--root is now the recommended single-bundle interface. Existing --project, --bundle, .md locators, custom aliases, and okf:// locators remain available. Migration checks and proposals never rewrite or accept catalog content automatically.

Verification

• 134 tests passed
• bundled OKF reference is conformant and project-valid
• packed-install and stdio MCP smoke test passed
• production-dependency audit reported no vulnerabilities

The npm publication of @mfdaves/okf-mcp@0.4.0 is intentionally separate from this GitHub release.

okf-mcp 0.3.3

Summary

This release focuses on MCP protocol correctness, predictable tool behavior, and accurate OKF link validation.

MCP initialization now supports protocol version 2025-11-25 and negotiates a preferred supported version for unknown revisions. The stdio transport now returns standard JSON-RPC error codes, ignores notifications correctly, keeps protocol output isolated from stderr, and distinguishes expected tool failures from transport failures.

Tool inputs are validated against their advertised schemas. Disabled authoring and remote-loading tools remain unavailable both in discovery and direct calls. list_concepts now honors its documented text query, and directory links resolve to nested reserved index.md documents for local, remote, and authoring validation paths.

The release also retains configured and runtime-loaded remote bundles after accepted local proposals. Package, CLI, MCP server, self-describing OKF bundle, and MCP Registry metadata all report version 0.3.3.

Install

npx -y @mfdaves/okf-mcp@0.3.3 --version
npx -y @mfdaves/okf-mcp@0.3.3 --project ./okf.project.yaml validate

Node 22 or newer is required.

Verification

The npm artifact was installed in a clean directory and verified through both packaged binaries, self-OKF validation, MCP 2025-11-25 initialization, tool discovery, resource reading, and concept retrieval. The full 69-test suite passes on Node 22 and Node 24.