okf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_bundlesA | List the local and remote OKF bundles currently loaded by the server. |
| list_conceptsA | List compact OKF concept summaries with optional bundle, type, tag, and text filters. |
| get_conceptA | Read one valid OKF concept, including its frontmatter, Markdown body, and links. |
| search_conceptsA | Search OKF concepts and return ranked summaries using text and structured filters. |
| list_typesA | Count the concept types present in the current OKF index. |
| list_tagsA | Count the tags present on concepts in the current OKF index. |
| list_relation_typesB | Count the typed relations present in the current OKF graph. |
| list_edge_kindsB | Count standard semantic and extension edge kinds in the current graph. |
| get_provenanceA | Trace normalized source provenance through internal concepts without fetching external resources. |
| inspect_attested_computationA | Statically inspect an Attested Computation contract and indexed inert artifacts; never execute it. |
| read_bundle_assetA | Read one explicitly referenced, already indexed bundle asset with digest verification and byte bounds. |
| read_git_sourceA | Read one pinned sources[].git entry from an explicitly mapped checkout or bare repository without fetching. |
| prepare_attested_computationA | Check declared parameters and produce non-executing digests without echoing parameter values. |
| check_computation_receiptA | Check receipt field presence only; never attest, echo values, or persist the receipt. |
| check_v02_migrationA | Analyze a local or remote bundle for safe staged OKF v0.2 migration without creating proposals or writes. |
| list_remote_bundlesA | List metadata for remote bundles currently loaded into the server. |
| okf_validate_conceptA | Validate a proposed new OKF concept without writing a proposal or concept file. |
| okf_suggest_concept_pathA | Suggest a safe bundle relative Markdown path from a concept type and title. |
| okf_list_proposalsB | List compact metadata for stored authoring proposals. |
| okf_get_proposalA | Read one authoring proposal, including its candidate content and validation result. |
| get_graphB | Return a bounded set of OKF graph nodes and edges with optional concept filters. |
| get_neighborsB | Return the incoming and outgoing graph relationships for one OKF concept. |
| get_subgraphB | Traverse a bounded OKF subgraph outward from one or more seed concepts. |
| find_pathsA | Find bounded relationship paths between two OKF concepts. |
| graph_summaryA | Summarize bundle, concept, edge, type, tag, and graph health counts. |
| validate_bundleA | Report OKF conformance separately from project validity for one bundle or the full current index. |
| validate_projectB | Report OKF conformance, project validity, and structured diagnostics for the complete configured project. |
| export_graphA | Render the current OKF graph as JSON, Graphviz DOT, or Mermaid text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Published okf-mcp Reference Bundle | Canonical public OKF bundle describing the okf-mcp product and its durable contracts. |
| okf-mcp Reference Bundle | reserved index.md |
| HTTP Authoring API | Optional local HTTP interface for validation and proposal-based concept authoring. |
| MCP Tool Catalog | Agent-facing tool contract for discovery, graph navigation, validation, producer execution, remote loading, and authoring. |
| okf-mcp | Project-agnostic OKF CLI, graph index, MCP stdio server, validated producer host, and authoring runtime. |
| Authoring Safety | Invariants protecting project boundaries, concept identity, review state, and concurrent edits. |
| File Concept Store | Local proposal, direct-batch, and concept persistence boundary used by root and project authoring. |
| OKF Indexer | Builds the validated in-memory document, concept, relation, and reference graph. |
| MCP Stdio Server | JSON-RPC stdio MCP runtime exposing OKF resources and tools. |
| Producer Host | Project-scoped runtime that loads allowlisted producers, validates strict OKF v0.2 candidates, and delegates safe publication. |
| Attested Computation Support | Static OKF v0.2 computation contract interpretation and non-execution boundary. |
| OKF Concept Format | Markdown and frontmatter contract consumed and produced by okf-mcp. |
| Pinned Git Sources | Host-agnostic source metadata and bounded local Git-object reads for code knowledge stored outside its source repository. |
| Producer API | Versioned Node.js contract for configured metadata producers that return candidate OKF v0.2 documents without publishing them. |
| Concept Authoring | Reviewable and direct workflows for validating and persisting structured OKF concept changes. |
| Concept Update | Guarded proposal workflow for correcting an existing OKF concept without losing concurrent changes. |
| Producer Publication | Preview and apply workflow for publishing validated producer-owned OKF v0.2 files without overwriting user-owned content. |
| OKF v0.2 Migration | Review-only compatibility migration for existing v0.1 and mixed knowledge catalogs. |
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.