Skip to main content
Glama
Aleksandrr

web-docs-mcp

by Aleksandrr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to web-docs-mcp

No user-submitted related servers found.

    Related Servers

    • Lookout

      SylphxAI
      A
      license
      Not graded
      quality
      B
      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.
      20 npm
      MIT

    • Findle

      jgraber
      A
      license
      Not graded
      quality
      C
      maintenance
      A fully local MCP server that provides web search via self-hosted SearXNG and page-to-markdown conversion (static and JS-rendered), all aggregated behind a single endpoint for use with AI assistants.
      MIT

    • beacon

      mason99-stack
      A
      license
      A
      quality
      C
      maintenance
      A zero-config MCP server that enables web search and page content fetching via DuckDuckGo, with no API keys or setup required.
      2
      MIT

    • Basic MCP Tools

      Tyguy047
      F
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server providing private web search, web page fetching, and current date/time tools, powered by a bundled SearXNG instance for API-key-free local search.
      2
      -

    • scrapyard

      artboarding-hash
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server for web search and page extraction, providing clean markdown from URLs, search results, site mapping, and research endpoints without API keys or accounts.
      5
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have clear boundaries: fetch_url retrieves a specific URL, lib_docs fetches library docs by name, list_docs works with local files. The main overlap is between web_search and search_docs, both performing web searches, though search_docs is specifically biased to official documentation and is local-first, which distinguishes it. Descriptions are detailed enough to disambiguate in practice.

    Naming Consistency4/5

    All names use lowercase snake_case with an underscore, and most follow a verb_noun pattern (fetch_url, search_docs, list_docs). However, web_search is noun_verb order and lib_docs is noun_noun, which are minor deviations from the dominant pattern. Overall the style is consistent and readable.

    Tool Count5/5

    Five tools is a well-scoped size for a documentation reference server. Each tool serves a clear function: web search, URL fetching, library-specific fetching, docs search, and local docs browsing. This is within the ideal 3-15 range and there is no bloat.

    Completeness5/5

    The tool set covers the full workflow for web documentation research: searching the web, fetching pages, retrieving library docs, searching with docs bias, and managing local saved docs. The optional saving via fetch_url and lib_docs, plus list_docs for browsing, avoids dead ends. No critical gaps are evident for the documented purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources