Skip to main content
Glama
Sign In
SioYooo

RepoGrammar

by SioYooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to RepoGrammar

No user-submitted related servers found.

    Related Servers

    • repo-context

      zyf0717
      A
      license
      D
      quality
      D
      maintenance
      Read-only repository context explorer for coding agents. Provides repository exploration tools via CLI or MCP adapter.
      1
      GPL 3.0
    • Euthynos by euthynos-org

      Euthynosofficial

      euthynos-org
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, read-only MCP server that provides AI coding agents with structural evidence about a repository, including dependency analysis and impact assessment, while naming the boundary of every answer without any LLM calls.
      21 npm
      Apache 2.0

    • token-context-mcp

      MCK564
      A
      license
      B
      quality
      A
      maintenance
      Enables coding agents to retrieve token-budgeted, source-hashed code context from explicitly registered local repositories via read-only MCP tools, reducing broad repository crawling while providing structure, symbols, and impact slices.
      10
      MIT

    • Sippion

      Sitten-Tokyo
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to retrieve focused, bounded repository context locally and read-only, reducing token usage while never modifying the repository or executing its code.
      -

    • codeloupe-mcp

      ndhkaeru
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to inspect files, search text, compare directories, read symbols, and apply structured edits against large codebases through bounded, local-first MCP tools.
      4
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation3/5

    With only one exposed tool there is no cross-tool selection risk, but that single tool internally multiplexes several distinct operations (find_analogues, explain_deviation, check_conformance, show_family, inspect_readiness, read_plan), and the boundary between them is only conveyed through a very dense prose description. An agent must parse a long block to know which mode to invoke and when, which is effectively ambiguity pushed inside one tool.

    Naming Consistency4/5

    The single name repogrammar_context is readable and uses a consistent snake_case prefix_noun convention. There is no pattern to violate with only one tool, but the namespace-prefixed form is coherent and predictable for any future additions.

    Tool Count2/5

    One tool for a surface that describes at least six distinct operations (pattern-family discovery, deviation explanation, conformance checks, family display, readiness/scoped-readiness inspection, change planning) plus setup/resync/autosync behavior is under-factored. The mega-tool approach forces mode dispatch and hidden branching, making the count too thin for the apparent scope.

    Completeness3/5

    The read-only analysis domain is partially covered: discovery, explanation, conformance, readiness, and planning are all reachable, and source-hydration is intentionally gated. However setup/resync/autosync are referenced only as behaviors of the same tool rather than distinct operations, and there is no explicit enumeration or listing of family ids beyond follow-up handles, leaving lifecycle steps implicit.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources