AgentCanon MCP
Related Servers
Alternatives to AgentCanon MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides 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.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables auditing and drafting of AI agent files (CLAUDE.md, AGENTS.md, Cursor rules) and turning project descriptions into full build specs, with local and API-based tools.47 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- AlicenseAqualityBmaintenanceUniversal bi-directional rules and prompt transpiler between Cursor (.cursorrules / .mdc), Claude Code (CLAUDE.md), and OpenAI with 98.5% certified AST parity and in-RAM secret redaction.341 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseCqualityDmaintenanceCaptures code modifications via AST analysis, generates reusable rules, and injects them into AI agent context with version audit and token-budgeted rule retrieval.288 npmApache 2.0
TDQS
Scored across 7 tools
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.
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.
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.
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.