Skip to main content
Glama
Sign In
Strands Agents MCP Server

Strands Agents MCP Server

Official
by strands-agents
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Strands Agents MCP Server

No user-submitted related servers found.

    Related Servers

    • okfy

      0dust
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.
      705 npm
      75
      MIT

    • Agentdocs

      Ricci62173
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to search and retrieve current technical documentation for supported agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP docs, CAMEL-AI, and CrewAI. It supports both stdio and SSE transport so documentation can be accessed locally or remotely.
      -

    • Agentdocs

      Dorothyb35
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to search and retrieve up-to-date technical documentation for popular agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel AI, and CrewAI. It does this by performing site-specific web searches and extracting page text through a standardized MCP interface over stdio or SSE.
      -

    • mcp-a2a-documentation

      martoc
      A
      license
      A
      quality
      B
      maintenance
      Search and retrieve Agent2Agent (A2A) protocol documentation using full-text search and section filtering.
      2
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: search_docs discovers relevant documentation URLs, while fetch_doc reads a specific page or section. The descriptions explicitly document the recommended search-then-fetch workflow, leaving little ambiguity.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun snake_case pattern: search_docs and fetch_doc. The slight singular/plural difference is natural and does not create confusion.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but for a focused documentation search-and-read server this is a clean, well-scoped surface. Each tool clearly earns its place.

    Completeness5/5

    The server covers the full retrieval lifecycle: search for documents, list catalog URLs, inspect document structure via TOC, and read specific sections or full small documents. No obvious documentation-access gaps remain.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources