Skip to main content
Glama
54334-bit

cumcm-rag-mcp

by 54334-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cumcm-rag-mcp

No user-submitted related servers found.

    Related Servers

    • ragifix-mcp by hephaistools

      ragifix-mcpofficial

      hephaistools
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables chat clients to search, add, retrieve, list, and delete documents in a ragifix knowledge base via MCP, plus health checks.
      -

    • mcp-rag-platform

      mittal-umang
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval-augmented question answering with source-grounded citations, document retrieval, and idempotent ingestion through MCP tools.
      -

    • studyproof

      Lapmlnex
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only search and context-pack creation over a local source library, letting AI assistants retrieve relevant excerpts and audit cited quotations.
      MIT

    • rag-mcp

      sakshipr14
      F
      license
      A
      quality
      C
      maintenance
      MCP bridge to a multimodal RAG service, enabling hybrid search and Q&A over documents with tools for knowledge base queries and health checks.
      4
      -
    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.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: search, document retrieval, source listing, and case-context assembly are well separated. However, rag_get_status and rag_health overlap in purpose, both probing system/index health, which could cause occasional misselection.

    Naming Consistency5/5

    All tools share the rag_ prefix and use consistent snake_case with action-oriented verbs like get, search, list, and health. The naming pattern is predictable and easy to extend.

    Tool Count5/5

    Six tools form a tight, well-scoped surface for a RAG retrieval server: search, document access, source metadata, context assembly, and health/status checks. No tool feels redundant or unnecessary.

    Completeness4/5

    The retrieval side is well covered: search, document reading, source listing, case context, and health checks. Minor gaps exist around index management or ingestion, but the apparent read-only RAG purpose is largely satisfied.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources