Skip to main content
Glama
nkapila6

mcp-local-rag

by nkapila6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-local-rag

No user-submitted related servers found.

    Related Servers

    • Open Agent Search

      jayanth-mkv
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted web search and page extraction for AI agents. Stdio MCP server, HTTP API and Python/npm CLI.
      59 npm
      57 PyPI
      2
      MIT

    • Lookout

      SylphxAI
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.
      42 npm
      1
      MIT

    • Wander

      ItzPhantomm
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and IDE harnesses to search the web and inspect pages through a native stdio Model Context Protocol interface, with fused results, caching, and prompt-injection protections.
      MIT

    • tavily-firecrawl-mcp

      bpzx
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server for web scraping and searching, with automatic fallback from Tavily to Firecrawl for fetching web content.
      2
      1
      MIT

    • Google PSE MCP Server

      rendyfebry
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables LLM clients like VSCode, Copilot, and Claude Desktop to search the web using Google Programmable Search Engine API.
      1
      20 npm
      12
      Apache 2.0
    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 6 tools

    Disambiguation3/5

    There is substantial overlap: rag_search_ddgs and deep_research_ddgs differ mainly by single-term vs multi-term querying, and rag_search_google mirrors deep_research_google. The bare `search` tool also competes with rag_search_ddgs, though its passage-level output and 'use this first' guidance help differentiate it.

    Naming Consistency4/5

    Most tools use a consistent snake_case, prefixed pattern (rag_search_* and deep_research_*). The bare `search` name and the parallel backend suffixes (`_ddgs`, `_google`) create minor inconsistency, but the overall naming remains readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for a web-search/RAG server. Each tool maps to a search mode (smart passage search, page search, deep multi-term research) with backend variants.

    Completeness4/5

    The surface covers single-query page search, passage search, and multi-term deep research across multiple engines. A direct fetch/extract-URL tool or explicit index-management operation is absent, but core research workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources