Skip to main content
Glama
seanchase-git

karpathy-wiki-mcp

by seanchase-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to karpathy-wiki-mcp

No user-submitted related servers found.

    Related Servers

    • brain-mcp

      rf-camillo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to safely read, search, and write an Obsidian vault kept as an LLM wiki, with index-first access, Obsidian-aware linking, and code-enforced guards for blocked folders, secrets, and write restrictions.
      7 npm
      MIT

    • LLM Wiki Kit

      iamsashank09
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables creation of persistent, compounding knowledge bases using Karpathy's LLM Wiki pattern with LLM-maintained markdown wikis. Supports automated ingestion, cross-referencing, synthesis, and linting of sources as an alternative to traditional RAG systems.
      61
      MIT

    • mcp-llm-wiki

      RickyKleinhempel
      A
      license
      A
      quality
      B
      maintenance
      Enables an LLM to autonomously maintain a Markdown-based wiki with YAML frontmatter, using hybrid BM25 and local CPU vector search for fully offline retrieval without external APIs or databases.
      18
      12 npm
      MIT

    • obsidian-vault-mcp

      lipereis
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI assistant to search, read, navigate links, and write only to the Inbox of a local Obsidian vault. It provides hybrid retrieval with reranking, restricted writing, and built-in evals for retrieval, tool use, and prompt injection.
      MIT

    • wikicore

      carlaost
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to build and maintain a shared, git-backed Markdown wiki: they search, file, update and link notes with YAML frontmatter, keep verbatim sources, and optionally read code repos, so knowledge one assistant records is available to all the others. Runs without LLM calls, embeddings or a database, with the vault's own files defining page types, instructions and tools.
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have crisp, distinct purposes: read vs. create vs. edit vs. delete vs. search vs. lint are clearly separated. The only mild overlap is among meta/read-ish tools (wiki_get_info, wiki_status, wiki_list, wiki_read), but descriptions distinguish them well (instructions vs. state overview vs. enumeration vs. content fetch).

    Naming Consistency5/5

    Every tool uses the same `wiki_` prefix followed by a snake_case verb or noun (wiki_read, wiki_create_page, wiki_delete_page, wiki_add_source). No mixed conventions or casing deviations.

    Tool Count5/5

    12 tools is well within the sweet spot and each tool maps to a distinct operation in the wiki lifecycle (bootstrap, source intake, page CRUD, search, lint, logging, status). Nothing feels redundant or padded.

    Completeness4/5

    The surface covers a full lifecycle: start sandbox, add raw sources, create/read/edit/delete pages, search, list, lint, log, and status. Minor gaps exist—no rename/move operation and raw sources cannot be deleted or edited, so some cleanup paths require workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources