Skip to main content
Glama

Related Servers

Alternatives to LangLa Server MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves documentation for Git repositories via MCP, providing tools to search docs, retrieve feature details, WIP status, and full context. Enables LLM agents to access human and LLM-optimized documentation through stdio or SSE transports.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes the Lichtblick documentation and the @lichtblick/suite extension API to AI agents over stdio, enabling full-text docs search, page fetching and listing, plus lookup and enumeration of exported TypeScript symbols with their doc comments.
      5
      Mozilla Public 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Serves bundled local engineering guidance—four instructions, a control Guide and 20 software engineering procedures—over local STDIO so coding agents can discover and read the right procedure for a task. It is read-only and stateless, leaving all project changes and permissions to the consuming agent.
      2
      Apache 2.0
    • 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.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to query and retrieve current technical documentation for popular agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel-AI, and CrewAI through stdio or SSE.
      -

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct access pattern: listing files, reading a whole file, searching free text, and looking up a specific MSG number. read_doc and get_msg overlap slightly since both return document content, but get_msg is clearly scoped to MSG-numbered entries, so an agent can choose reliably.

    Naming Consistency4/5

    Four of five tools follow a clean verb_noun pattern (read_doc, list_docs, search_docs, get_msg). server_overview breaks the pattern by being noun-only, a minor but noticeable deviation.

    Tool Count5/5

    Five tools is well-scoped for a documentation-retrieval server, with each tool covering a distinct lookup strategy. No redundant or filler tools.

    Completeness4/5

    The surface covers the core docs workflow: overview, listing, full read, free-text search, and targeted MSG lookup. Minor gaps exist, such as no way to enumerate all MSG entries or page through very large documents, but agents can work around these via search_docs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues