Skip to main content
Glama
jamesonBradfield

lightrag-docs-rag-mcp

by jamesonBradfield
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to lightrag-docs-rag-mcp

No user-submitted related servers found.

    Related Servers

    • lightrag-mcp

      TimaxLacs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a persistent LightRAG knowledge base through any MCP client, offering both ready-made answers with source links and raw context retrieval for custom response generation.
      34 npm
      MIT

    • mcp-rag-bridge

      zyay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and manage a document knowledge base via MCP, with RAG-powered search and grounded answers with citations.
      MIT

    • LightRAG MCP Server

      nailmailster
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to interact with a LightRAG knowledge graph server via MCP, providing 30 tools for queries, document management, and graph operations.
      34 npm
      MIT

    • lightrag-mcp

      shemhamforash23
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that bridges LightRAG API with MCP-compatible clients, enabling retrieval-augmented generation, document management, and knowledge graph operations.
      122
      -

    • Cognify MCP Server

      S3YED
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables document ingestion and typed knowledge graph queries through Claude MCP tools, allowing agents to extract, store, and retrieve typed entities and relations from documents.
      2
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: querying the graph, ingesting documents, and inspecting instance state. No two tools could be confused for one another.

    Naming Consistency5/5

    All tool names follow a consistent docs_ prefix with a clear verb suffix (query, ingest, stats). The pattern is uniform and predictable.

    Tool Count5/5

    Three tools cover the core RAG lifecycle (ingest, query, monitor) without redundancy. This is a well-scoped set for a focused documentation assistant.

    Completeness4/5

    The essential operations are present: adding documents, retrieving answers, and checking status. A delete or clear operation is the only notable gap, but it is not critical for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources