Skip to main content
Glama
Rules MCP Server

Rules MCP Server

My Rules

An MCP server for all my rules, prompts, etc etc. Allows agents to call rules on demand.

There's no point filling 4 paragraphs of instructions for how to write tests if your current session isn't going to write a test.

Spiritually similar to Cursor's rules.

Usage

Claude Code

claude mcp add --transport http rules https://mcp.cianfrani.dev/mcp

Cursor

Install MCP Server

Claude Desktop

{
    "rules": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.cianfrani.dev/mcp"
      ]
    }
}

Related MCP server: keystone-mcp

What's It Do?

Allows coding agents to lookup rules on demand within the context of their current task.

> write a test for @calc.py
  ⎿  Read calc.py (26 lines)

⏺ rules:get_rules_for_writing_tests (MCP)(language: "python")
  ⎿  - Before testing a protected method, ask "Can this logic be adequately tested through the public interface?". If yes, don't test the protected method directly.
     If no, continue testing the protected method.
     - Remember to write tests using the Arrange, Act, Assert pattern.
     … +12 lines (ctrl+r to expand)

⏺ Write(test_calc.py)

Why?

  • It's really annoying trying to carry all these little notes between projects/IDEs.

  • I don't want to have to manually invoke rules.

How's It Work?

Clearly-defined tool descriptions allow the agent to fetch rules on demand, only if they appear to be relevant.

What Doesn't work?

  • Patterns must be associated with a specific action. For example, "writing tests", "authoring UI", "reviewing a PR".

  • The agent ultimately decides if it's going to call the tool. Sometimes it does. Sometimes it doesn't.

Tools

  1. get_rules_for_writing_tests

    • Use when: writing any type of test,

    • Inputs:

      • language (string)

  2. get_rules_for_composing_ui

  • Use when: creating new frontend components

Prompts

In Claude Code, invoke prompts as slash commands.

  1. pr-review

Resources

Dev

  1. Start the server

npm run dev
  1. Open MCP inspector

npm run inspect

Available Tools

2 tools
get_rules_for_composing_uiA
        Use when: creating new frontend components, designing component APIs, structuring component hierarchies, implementing component interactions, or making styling decisions.

        What it provides: Comprehensive guidelines for creating new UI components.

        How to use: Invoke this tool at the START of any UI component work to retrieve user-specific UI patterns and preferences, then follow these guidelines throughout the component lifecycle.
    

Inputs: no named parameters.

get_rules_for_writing_testsA
      Use when: writing any type of test, modifying existing tests, reviewing test structure, or making decisions about test implementation. 

      What it provides: User-specific rules, patterns, and preferences for test composition including naming conventions, structure, assertions, mocking approaches, and coverage requirements.

      How to use: ALWAYS invoke this tool BEFORE writing or modifying any test code to retrieve the current testing guidelines, then apply these rules throughout your implementation.
    

Inputs: language (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one is for UI component composition and the other is for test writing. Their descriptions specify non-overlapping domains (frontend UI vs. testing), making misselection unlikely.

    Naming Consistency5/5

    Both tools follow a consistent 'get_rules_for_verbing_noun' pattern with snake_case. This predictable naming scheme makes it easy to understand their function at a glance.

    Tool Count2/5

    With only 2 tools, this server feels thin for a 'Rules MCP Server' that presumably handles various development guidelines. The scope implied by the server name suggests more rule categories (e.g., backend, documentation, deployment) would be expected.

    Completeness2/5

    The server covers only UI and testing rules, leaving significant gaps for other development domains like API design, database interactions, security practices, or deployment. This incomplete surface will likely cause agent failures when broader rule guidance is needed.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers