mcp-rule-engine
Related Servers
Alternatives to mcp-rule-engine
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
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce token usage and context bloat through AST skeletonization, prompt distillation, caching, and token-budget governance while preserving essential code context.1311,938 npm46MIT
- AlicenseBqualityDmaintenanceEnables LLMs to access AST-based code structure maps, token-efficient skeletons, and analyze diff impact and blast radius for regression testing.36 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve budgeted, AST-aware edit context and run refactor-safety checks over a local Tree-sitter code knowledge graph, reducing token use by avoiding full-file reads.52 PyPI4MIT
- AlicenseBqualityBmaintenanceEnables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.25238 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables automatic knowledge capture and injection of guardrails for AI assistants like Claude and Cursor, improving code quality and preventing recurring mistakes.15 npmMIT
TDQS
Scored across 28 tools
Most tools have distinct purposes (e.g., session, webhook, plugin groups), but 'capture_diff' and 'analyze_workspace' both analyze diffs for rule violations, and 'query_rules' vs 'list_rules' overlap in listing rules. This causes minor ambiguity.
All tools follow a consistent verb_noun pattern using snake_case, with domain prefixes (cognition_, governance_) applied uniformly. No mixed conventions or irregularities.
28 tools is slightly above the typical well-scoped range (3-15). The broad domain (rule management, cognition, sessions, webhooks, plugins) justifies the count, but it feels heavy for a single server.
Core rule lifecycle (create via generate, confirm/edit, list, query, resolve conflicts) is covered, but a 'delete_rule' tool is missing. Session, webhook, and plugin management appear complete, leaving minor gaps.