Skip to main content
Glama
Sign In
AtlasRepo MCP

AtlasRepo MCP

by Arnon-hs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AtlasRepo MCP

No user-submitted related servers found.

    Related Servers

    • RepoKnow MCP

      gdpu11
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to read-only query a self-hosted repository knowledge base, searching documents, source code, and symbols across GitHub and GitLab imports while retrieving source and dependency traces by commit and path.
      3
      MIT

    • docu

      CharlyZeta
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to generated technical documentation across one or multiple documented repositories, exposing tools to search code and docs, inspect modules and symbols, list gaps, review architecture, and check freshness with file#line citations.
      MIT

    • capalith

      Kayhusk
      A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to a local-first catalog of portable agent skills, exposing tools to discover ranked matches, inspect stored artifacts, traverse declared relationships, and view configuration.
      5
      MIT
    • mentu-navigator-mcp

      mentu-navigator-mcpofficial

      mentu-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only, provenance-first repository navigation for agents and humans, with ranked lexical retrieval, exact query, document handles, symbol context, and change impact analysis.
      90 npm
      Apache 2.0
    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.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are mostly distinct: atlasrepo_recommend is problem-driven, atlasrepo_search_tools is structured query-based, and atlasrepo_get_repository is a targeted detail fetch. However, recommend and search_tools could both return repositories/tools, so an agent might occasionally be unsure which path to use for discovery.

    Naming Consistency4/5

    All tools share the atlasrepo_ prefix and use a verb-first style. atlasrepo_search_tools and atlasrepo_get_repository follow a clear verb_noun pattern, but atlasrepo_recommend lacks an object, creating a minor inconsistency.

    Tool Count5/5

    Three tools is well-scoped for this domain: one for problem-level recommendation, one for structured search, and one for inspecting a specific repository record. Each tool covers a distinct part of the workflow without redundancy.

    Completeness4/5

    The read-only decision-record workflow is well covered: discover by problem, search by criteria, and load detailed evidence for a repository. Minor gaps include no explicit list-all/browse capability or a dedicated workflow-detail fetch, but these are workable through the existing tools.

    Resources