Skip to main content
Glama

Related Servers

Alternatives to cody-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to search and read offline documentation from synced libraries via MCP tools, providing hybrid keyword and semantic search without network calls.
      8 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to search and read Anahita's documentation and API reference locally, so agents can answer current questions about setup, federation, routes, parameters, and response shapes, including offline from cached copies.
      6
      90 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search and read a local library of saved prompts, skills, MCP servers, and design boards, fill prompt blanks, and retrieve board design briefs through read-only, offline tools, prompts, and resources.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search and retrieve approved, role-filtered internal knowledge with PII redaction, citations, content-integrity checks, and tamper-evident audit logging.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables hybrid search over product PDFs with version-aware, figure-returning answers for any MCP client, locally or via secure remote access.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides LLM-free search tools across Confluence, JIRA, code, and project knowledge for any MCP client.
      3
      MIT

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation3/5

    ask_cody and search_team_knowledge both retrieve information about Cody, so an agent could confuse them for question-answering tasks. list_integrations is clearly distinct, but the overlap between the other two creates some ambiguity.

    Naming Consistency5/5

    All tools use snake_case with a verb_noun pattern (search_team_knowledge, list_integrations, ask_cody). The style is consistent and predictable.

    Tool Count5/5

    Three tools is well within the ideal range and each targets a distinct retrieval need: knowledge search, integration listing, and Q&A. No unnecessary tools.

    Completeness4/5

    The surface covers the core informational needs (search, list, ask), but lacks a dedicated tool to fetch full article or integration details. Agents can work around by following canonical URLs.