Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@waymark show me the concept for src/main.rs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server exposing a codebase's OKF
knowledge bundle (okf/) to Claude Code — three schema-enforced query
tools instead of raw Read/Grep over hand-written docs.
list_concepts(type?, tags?) — frontmatter-only summaries. tags matches
any-of the given tags.
read_concept(path) — full frontmatter + body for one concept, by the
path a list_concepts call returned.
find_concept_by_resource(file_path) — reverse lookup: which concept(s)
describe a given source file.
The server is stateless — it re-reads okf/ from process.cwd() on every
call, so there's nothing to invalidate when concept files change.
Related MCP server: claudecode-mcp
npx -y @aleburrascano/waymark initThis registers everything a repo needs in one step:
Adds a waymark entry to .mcp.json (creating it if missing).
Installs a pre-commit hook at .git/hooks/pre-commit that blocks commits
when a resource-mapped file changes without its okf/ concept being
updated. Safe to re-run — it upgrades its own hook on later waymark
versions but never overwrites a hook it didn't install.
Installs two skills to .claude/skills/: okf-staleness-fix (the
writer/judge playbook Claude Code uses to resolve a blocked commit) and
okf-bootstrap (the propose/approve/generate/judge playbook Claude Code
uses to seed an initial okf/ bundle).
Adds (or refreshes) an ## OKF context section in the repo's CLAUDE.md.
Run it again any time to pick up updates from a newer waymark version.
okf/ bundles don't have to be hand-written from scratch. After running
waymark init, ask Claude Code to bootstrap one:
"Bootstrap okf for this repo"
This invokes the okf-bootstrap skill, which:
Runs waymark bootstrap — a deterministic scan (git ls-files-based,
respects .gitignore) that lists every candidate source file.
Proposes a candidate concept list grouped by domain (one concept per named unit you'd naturally ask "what is X" about) — nothing is written yet.
Waits for your approval, or feedback to re-group/rename/split candidates.
Generates each approved concept, verified by a judge subagent before it's written to disk.
Stages the new files with git add and reports what was generated —
committing is left to you.
This is a one-time, human-supervised pass. Ongoing drift after that is
caught by the pre-commit hook and okf-staleness-fix skill, not by
re-running bootstrap.
npm install
npm test
npm run build && npm link # then `waymark` runs the built CLInpm test runs vitest against TypeScript source directly — no build step
required for the test suite.
Find the OKF concept(s) whose "resource" field matches a given source file path — reverse lookup from code to the concept describing it.
Inputs: file_path (required).
List OKF concept summaries (frontmatter only) from this repo's okf/ bundle, optionally filtered by type and/or tags.
Inputs: tags, type.
Read the full frontmatter and body of one OKF concept by its path (relative to the repo root, as returned by list_concepts).
Inputs: path (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool targets a distinct operation: listing summaries, reading a specific concept by path, and reverse lookup by resource. No overlaps or ambiguity.
All tools follow a consistent verb_noun pattern (list_, read_, find_) with snake_case. The naming is uniform and predictable.
3 tools is a minimal but reasonable scope for a read-only concept bundle server. It's slightly on the lean side but not inappropriately so.
Covers the core read workflows: list all concepts, read a specific one, and reverse lookup by resource. Lacks create/update/delete, but that may be outside the intended purpose.
Repository knowledge graph MCP server for codebase understanding and debugging.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
