Skip to main content
Glama
Sign In
cairn

cairn

by Moe1177
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cairn

No user-submitted related servers found.

    Related Servers

    • Glasir

      Attackwave
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding assistants to query a deterministic local graph of repository definitions, references, dependencies, and change impact, returning bounded evidence for questions such as what calls a symbol, what breaks when it changes, and how two symbols connect.
      Apache 2.0

    • cross-repo-graph

      arsen-superman
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives coding agents a read-only, token-budgeted code graph spanning every repository in a project: symbols, calls, imports, and cross-repo HTTP, config, and package links, each backed by file:line evidence on both sides. This lets agents trace how symbols connect across repos and determine the impact of an API change by distinguishing links that are actually used from ones that are only declared.
      534 npm
      Apache 2.0

    • Kivgraph

      Luqueee
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to query a semantic cross-repository code graph for symbols, references, callers, dependencies, and change impact across registered repositories.
      12
      23
      Apache 2.0

    • TokenSaver MCP

      KaryawanSurga
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to get a compact, token-budgeted map of any repository in one call, including file tree, language stats, entry points, and key symbols, so they read only what they need.
      4
      1
      MIT
    • spine

      spineofficial

      SylphxAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides local-first repository architecture analysis with file-level proof, enabling agents to map codebases, locate implementations, trace call paths, and assess change impact with deterministic evidence.
      4 npm
      11
      MIT

    • LayerMap

      coffeecoproject
      A
      license
      A
      quality
      B
      maintenance
      Gives coding agents read-only tools that return, in one call, a declaration's callers traced up to entry points or its callees down to 8 levels, plus a map of directories, files, declarations and every usage of a symbol. Maps TypeScript, JavaScript, Go, Python and Java using each language's own compiler, so a change's impact can be traced across imports, methods, interfaces and decorators.
      4
      1,938 npm
      9
      Apache 2.0
    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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: repo resolution, repo cards, remote file reads, refresh, org profiling, package lookup, and several scoped search modes. There is some overlap between links and related, between org_packages and org_profile, and among query, find_similar, search_org, and find_across, but the descriptions provide enough boundaries to guide selection.

    Naming Consistency3/5

    The names are all snake_case and readable, but they mix verb-led names (resolve_repo, read_org_file, find_across, search_org) with noun/adjective labels (repo_card, links, related, org_packages, org_profile). The convention is not chaotic, but it is not a predictable verb_noun pattern throughout.

    Tool Count5/5

    Twelve tools is a reasonable size for an org-scale code intelligence server spanning repo discovery, relationship mapping, package lookup, local/remote search, and refresh operations. Each tool appears to cover a meaningful slice of that workflow rather than padding the surface.

    Completeness4/5

    The surface covers the main read-only code intelligence lifecycle: finding repos, understanding them, mapping links and dependencies, locating org packages, searching local and remote code, finding similar implementations, reading remote files, and refreshing state. A minor gap is the lack of an explicit workspace/org repository listing tool, but resolve_repo and related discovery tools largely work around that.

    Resources