Skip to main content
Glama
frankchu91

MindBase

by frankchu91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MindBase

No user-submitted related servers found.

    Related Servers

    • LLM Wiki MCP

      jlnkrth
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.
      18 npm
      1
      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

    • vault-mcp

      Lincyaw
      A
      license
      A
      quality
      D
      maintenance
      Markdown + SQLite knowledge store with bidirectional wikilinks, exposed as an MCP server for AI agents to maintain an interconnected knowledge base.
      11
      MIT
    • Chilon Recall by ctrlcakepro

      Chilon Recallofficial

      ctrlcakepro
      A
      license
      A
      quality
      A
      maintenance
      Local-first knowledge retrieval MCP server that turns private text documents into a source-backed knowledge base, enabling retrieval, comparison, summaries, and review outlines for any local MCP client while keeping source paths and index operations visible.
      13
      437 npm
      2
      MIT

    • obsidian-wiki-mcp

      aud1ence
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that implements Karpathy's LLM Wiki pattern for Obsidian vaults, enabling persistent knowledge storage and BM25 search across AI sessions.
      10 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 50 tools

    Disambiguation2/5

    There are five different search/retrieval entry points (search_wiki, search_all_projects, semantic_search, search_in_project, ask_wiki) whose selection criteria overlap heavily, and multiple ingest-like tools (ingest_source, ingest_plan/execute, quick_capture, save_chat_excerpt, mindbase_ingest_file) that an agent could easily conflate. Despite good individual descriptions, the boundaries between them are too subtle for reliable automatic tool selection.

    Naming Consistency2/5

    The tool names mix a clean simple verb_noun convention (search_wiki, create_note, list_feeds) with a large prefixed mindbase_* family (mindbase_init_project, mindbase_atomic_write_context, mindbase_rebuild_index). Across the set there is also inconsistent terminology for seemingly similar resources: review cards vs cards, notes vs wiki pages, search vs query, and ingest vs capture.

    Tool Count2/5

    50 tools is a very large surface for a single MCP server, crossing several domains: wiki operations, projects, RSS, spaced repetition, chat recall, and internal v2 project management. The count exceeds what an agent can reliably reason about, and many tools appear to be internal project-workflow helpers rather than user-facing knowledge-base operations.

    Completeness2/5

    Core create/read/update/search functionality exists for notes, but there is no delete/archive for wiki pages, no feed removal, no review-card update/delete, and no way to list all pages beyond recent activity. The tool surface has several dead ends that will force agents into awkward workarounds, although rich project-level operations are covered.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources