Skip to main content
Glama
Sign In
justinmclean

Iggy Docs MCP

by justinmclean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Iggy Docs MCP

No user-submitted related servers found.

    Related Servers

    • Documentation Fetcher & RAG

      mikkelkrogsholm
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to fetch, index, and perform semantic RAG-based searches on API documentation from various sources. It provides tools for hybrid search and collection management, allowing users to access up-to-date documentation from projects like Gemini and FastMCP.
      -
    • LaserData Docs MCP by laserdata

      LaserData Docs MCPofficial

      laserdata
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to answer Laser SDK and LaserData Cloud questions from current documentation instead of training data, drawing on both the guides website and the public Python API surface. It provides ranked search, full-page retrieval, code example discovery, and related-page navigation across both corpora.
      8
      Apache 2.0

    • Agentdocs

      nicholas5568
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI models 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 via stdio or SSE transports.
      -
    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 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing, fetching, searching, finding examples, extracting snippets, getting related docs, explaining structure, checking links, and refreshing. Even search_docs and find_examples are well-separated by their focus on general search versus example discovery.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_docs, get_doc, search_docs, find_examples, extract_code_snippets, get_related_docs, explain_doc_map, find_broken_links, refresh_docs). The pattern is predictable and easy to infer.

    Tool Count5/5

    Nine tools is well-scoped for a documentation server. Each tool covers a distinct aspect of doc navigation, search, extraction, and maintenance without unnecessary redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of documentation access: discover, retrieve, search, extract examples, find related content, understand structure, validate links, and refresh data. No obvious gaps for a read-only docs MCP.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources