Skip to main content
Glama
aws-powertools

Powertools MCP Search Server

by aws-powertools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Powertools MCP Search Server

No user-submitted related servers found.

    Related Servers

    • mcp-server-docy

      oborchers
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides documentation access capabilities. This server enables LLMs to search and retrieve content from documentation websites by scraping them with crawl4ai. Built with FastMCP v2.
      18
      MIT

    • MCP-Ragdocs

      qpd-v
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that enables semantic search and retrieval of documentation using a vector database (Qdrant). This server allows you to add documentation from URLs or local files and then search through them using natural language queries.
      17 npm
      136
      Apache 2.0

    • mcp-ragdocs

      hannesrudolph
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context
      9 npm
      265
      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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: search_docs finds relevant documentation pages, while fetch_doc_page retrieves the content of a specific page. There is no overlap in functionality, and the descriptions explicitly state the workflow relationship between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (search_docs, fetch_doc_page) with clear, descriptive names that match their functions. The naming is uniform and predictable throughout the set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a documentation search domain. While the tools cover the core search-and-retrieve workflow, additional utilities like listing available versions or filtering by runtime could enhance completeness. The count is borderline but functional.

    Completeness4/5

    The toolset covers the essential documentation search workflow: finding pages and fetching content. However, there are minor gaps, such as no direct way to list documentation sections or filter searches by runtime/version without relying on search queries. Agents can work around these with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources