Skip to main content
Glama
Sign In
knowledge-library-mcp

knowledge-library-mcp

by kennyrnwilson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to knowledge-library-mcp

No user-submitted related servers found.

    Related Servers

    • clinic-mcp-server

      leomengineer
      F
      license
      A
      quality
      D
      maintenance
      Exposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.
      4
      -

    • edith

      Rchari1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read and search a local Markdown knowledge base and past session transcripts, and write distilled notes back into it over MCP.
      15 npm
      1
      MIT

    • Claude-Desktop-Bridge

      KiMiGuel
      A
      license
      A
      quality
      B
      maintenance
      Enables a shared persistent knowledge vault for Claude Desktop, allowing notes to be saved, retrieved, searched, updated, and deleted across Chat and Code tabs.
      5
      68 npm
      MIT

    • samong-mcp

      waanvar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code and Claude Desktop to search, read, and write a local-first Markdown knowledge base so users' notes act as persistent agent memory across sessions.
      2
      Apache 2.0

    • secondbrain-mcp

      TomLous
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude clients to search, read, and write to a Markdown second brain vault via GitHub, with tools for retrieval, capture, and knowledge graph consistency.
      -
    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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: areas, note content, searches, projects, and git operations are cleanly separated. Even the retrieval tools differ clearly by path-based access, guidance-specific lookup, and area-scoped listing.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_* for collections, get_* for single items, create/update/append for mutations, and save/list for git workflow. The naming makes the tool set predictable and easy to navigate.

    Tool Count5/5

    11 tools is well-scoped for a knowledge library covering capture, search, retrieval, editing, project listing, and git persistence. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    The surface covers create, read, update, search, capture, project listing, and git commit/push workflows. Missing delete/archive and a general list-all-notes operation are workable gaps, but they may be intentional for a permanent knowledge base.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources