okf-mcp
Related Servers
Alternatives to okf-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that enables full-text search and link navigation over Markdown files as a knowledge graph.-
- AlicenseNot gradedqualityAmaintenanceMCP server that turns a Markdown folder (e.g. Obsidian vault) into a second brain, capturing readings and ideas, connecting them as concepts, and resurfacing related notes on demand.28 npmMIT

neuphlo-mcpofficial
FlicenseNot gradedqualityBmaintenanceMCP server for a Markdown-backed knowledge repository, offering tools for searching, retrieving, validating, and authoring records, plus MCP Apps that render dashboards and inline tables in compatible clients.-- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to search, fetch, and analyze a self-maintaining markdown knowledge base with provenance, drift detection, and canonical definitions.1MIT
- AlicenseAqualityCmaintenanceMCP server that indexes Markdown, Word, HTML, and PDF documents into a SQLite knowledge graph with CJK+Latin full-text search and cross-document reference tracking. Runs drift audits to surface stale policies, conflicting research claims, superseded ADRs, and undocumented code exports.108MIT
- FlicenseNot gradedqualityCmaintenanceA CLI tool and MCP server that turns markdown documentation into a searchable, queryable knowledge base.74 npm-
TDQS
Scored across 28 tools
Most tools have distinct purposes, but there is overlap between list_remote_bundles and list_bundles, and validate_bundle vs validate_project could confuse. Descriptions help clarify boundaries, but the redundancy slightly hurts disambiguation.
Naming mostly follows verb_noun pattern (list_, get_, validate_, etc.), but there are inconsistencies like graph_summary (not a verb) and the okf_ prefix applied only to some tools (okf_validate_concept vs validate_bundle). These are minor deviations.
28 tools exceed the 25+ threshold for too many. While the domain is complex, several tools are redundant (e.g., list_remote_bundles vs list_bundles) and many listing tools could be combined, making the surface feel bloated.
The server is read- and validation-heavy, with no create/update/delete operations for concepts or bundles. Proposals are only readable, and there is no tool to author or modify content, leaving significant lifecycle gaps for an authoring-oriented domain.