Skip to main content
Glama
AgentCanon MCP
by touhi13

Related Servers

Alternatives to AgentCanon MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with queryable, version-controlled project rules and coding standards. Enables validation, rule-based guidance, and task summaries to keep AI work aligned with your project's conventions without repeating context.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code, Cursor, Codex, and Claude Desktop to carry project decisions, rules, bugs, to-dos, and failed approaches across sessions by saving them as lines in a repo file and bringing the relevant ones back on each prompt. It also checks commands and file edits against those saved rules before they run, flagging anything that might break one.
      169 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous-agent runs to be verified through a deterministic seven-gate pipeline and cryptographically attested with RFC 6962 SHA-256 Merkle proofs, including selective-disclosure inclusion proofs and GitHub pull-request attestation cards.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Captures code modifications via AST analysis, generates reusable rules, and injects them into AI agent context with version audit and token-budgeted rule retrieval.
      28
      8 npm
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the rule-management lifecycle: inspection, import, listing, single-rule mutation, validation, plan generation, and plan application. The preview_sync/apply_sync pair is explicitly separated by the approval-bound planId contract, so there is no risk of confusing them. No two tools overlap in purpose.

    Naming Consistency5/5

    All seven names use a consistent snake_case verb_noun pattern (inspect_project, list_rules, upsert_rule, validate_rules, preview_sync, apply_sync). Even the longer import_existing_rules follows the same verb-first convention.

    Tool Count5/5

    Seven tools is a tight, well-scoped surface for a rule-canonicalization workflow, and each tool maps to a necessary step (read, import, list, write, check, plan, apply). Nothing appears redundant or missing from the count alone.

    Completeness4/5

    The core lifecycle from inspection through import, editing, validation, and guarded sync is fully covered. Minor gaps remain: there is no delete_rule or get_rule for fine-grained single-rule access, and no rollback/revert operation after apply_sync.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues