Commands

A dedicated MCP server for managing and calling your rules on demand. It enables agents to look up and apply rules within their current task, streamlining testing, UI work, and other repetitive actions across projects.

How to use

Connect your MCP client to the server to fetch and apply rules as you work. You can use a remote MCP URL to access the rules, or run a local MCP client that talks to the server directly.

Two common approaches are available: a remote HTTP endpoint and a local stdio client that invokes MCP commands from your environment. The HTTP option lets you call the server over the network, while the stdio option runs a command locally to query and apply rules as part of your task workflow.

Typical workflows include looking up a rule before performing a task, such as writing tests or composing UI, and then applying the rule's guidance inside your editor or test suite. The system decides when a rule is relevant and can fetch it on demand based on the action you describe.

How to install

Prerequisites: ensure you have Node.js installed on your system. You can verify by running node -v and npm -v.

1. Install the MCP client or runner that you will use to connect to the server. If you choose the remote approach, you don’t need a local server run step beyond starting your client.

2. If you prefer a local setup, install and run the MCP runner as described in the examples. The local command uses the MCP URL to talk to the server.

Examples and tips

The server exposes rules that agents can fetch on demand. For instance, when you are asked to write tests, you can pull the relevant testing rules for your language and apply them to your codebase.

Here are explicit examples of how you might connect in both HTTP and stdio modes. Use these as templates for your own setup.

{
  "mcpServers": {
    "rules_http": {
      "type": "http",
      "name": "rules_http",
      "url": "https://mcp.cianfrani.dev/mcp",
      "args": []
    },
    "rules_stdio": {
      "type": "stdio",
      "name": "rules_stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.cianfrani.dev/mcp"]
    }
  }
}

Notes on usage and capabilities

• Patterns must be tied to a specific action like writing tests or composing UI. The agent decides whether to call a rule based on the task context.

• Using rules reduces back-and-forth between projects and IDEs by providing on-demand guidance within your task context.

Available tools

get_rules_for_writing_tests

Fetches applicable rules when writing tests for a given language, helping ensure tests follow best practices and are aligned with project conventions.

get_rules_for_composing_ui

Fetches rules for creating frontend UI components, guiding structure, accessibility, and consistency.

pr-review

Provides a structured template to review a unit of work and give actionable feedback.