Skip to main content
Glama
riemannulus

knowledge-base

by riemannulus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to knowledge-base

No user-submitted related servers found.

    Related Servers

    • agent-lore

      osteele
      A
      license
      Not graded
      quality
      B
      maintenance
      A machine-local, agent-writable knowledge base MCP server that lets coding agents autonomously record and retrieve hard-won operational facts, incidents, and corrections as markdown pages in a git repo, with provenance, talk pages, and search.
      4 npm
      MIT

    • mulchd

      ChacheGS
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for storing and serving structured team knowledge, enabling AI sessions to load relevant team context without re-prompting.
      Apache 2.0

    • rag-mcp

      mmelmesary
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-capable LLM client to search self-hosted long-term memory over markdown and PDF documents, combining dense semantic vectors with BM25 keyword retrieval and optional cross-encoder reranking. Exposes a read-only tool surface for querying incidents, runbooks, and other knowledge-base content, while writes happen out-of-band through ingestion jobs or a token-gated internal API.
      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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools serve clearly distinct purposes, with detailed descriptions clarifying edge cases (e.g., search_code vs. search vs. subsystem_index). Minor overlap exists between search and pitfalls, but their intents are well explained.

    Naming Consistency3/5

    The majority follow a verb_noun pattern (record_*, search_code, get_document), but 'search' and 'pitfalls' deviate, and 'subsystem_index' uses a noun_noun format. This mixing makes the convention less predictable.

    Tool Count4/5

    15 tools is at the upper boundary of a well-scoped set. Each tool has a defined role, though a few meta-tools (search_feedback, stale_notes) add complexity without being strictly necessary for core knowledge-base operations.

    Completeness4/5

    Covers search, retrieval, creation/updating via record_* idempotency, verification, and catalog listing. Missing an explicit delete tool, but supersedes mechanism partially addresses retirement. Overall, the surface is quite complete for its stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources