Skip to main content
Glama
ndjordjevic

PinRAG

by ndjordjevic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to PinRAG

No user-submitted related servers found.

    Related Servers

    • mcp-rag-server

      kwanLeeFrmVi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that indexes documents and serves relevant context to LLMs via Retrieval Augmented Generation (RAG).
      25 npm
      37
      MIT

    • MCP RAG

      santis84
      A
      license
      B
      quality
      D
      maintenance
      A complete MCP server for Retrieval-Augmented Generation with file management and vector memory for agents. Supports multiple document formats (PDF, DOCX, TXT, MD, CSV, JSON) with semantic search using Hugging Face embeddings and ChromaDB for efficient vector storage.
      11
      3 npm
      1
      MIT

    • nexla-document-qa-mcp

      PShinde630
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that answers natural language questions over a collection of research PDFs, using semantic retrieval and Gemini for grounded answers with citations.
      -

    • ragvault

      maxrotemberg04-spec
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local-first RAG over Obsidian vaults, enabling AI agents to search and ask questions about notes with grounded citations.
      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.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools have mostly distinct purposes with clear boundaries: adding documents, listing documents, querying, and removing documents. However, there is some ambiguity between add_document_tool and add_url_tool since both handle URLs (GitHub/YouTube), though the descriptions clarify that add_document_tool is for mixed inputs while add_url_tool is URL-specific. This slight overlap could cause minor confusion but is mitigated by descriptive tool names and clear documentation.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun_tool pattern (e.g., add_document_tool, list_documents_tool, query_tool, remove_document_tool). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style or convention across the five tools.

    Tool Count5/5

    With 5 tools, this server is well-scoped for its RAG indexing and querying purpose. Each tool serves a clear, essential function (add, list, query, remove) without redundancy, and the count aligns with typical MCP server ranges (3-15 tools), ensuring the set is neither too sparse nor overloaded.

    Completeness4/5

    The tool surface covers the core CRUD lifecycle for a RAG system: adding documents (including URLs), listing indexed documents, querying with filters, and removing documents. A minor gap is the lack of an update tool for modifying indexed documents (e.g., re-indexing or updating tags), but agents can work around this by removing and re-adding. Overall, the coverage supports basic workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources