https://github.com/markacianfrani/mcp-pattern-language
https://github.com/markacianfrani/mcp-pattern-language
Last synced: 5 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/markacianfrani/mcp-pattern-language
- Owner: markacianfrani
- Created: 2025-06-19T20:20:58.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2025-06-19T22:26:27.000Z (5 months ago)
- Last Synced: 2025-06-19T22:29:17.810Z (5 months ago)
- Language: TypeScript
- Size: 17.6 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- toolsdk-mcp-registry - ❌ pattern-language - specific rules through a tool-based interface that processes markdown instruction files into executable patterns. (node) (Coding Agents / How to Submit)
README
# 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
[](https://cursor.com/install-mcp?name=rules&config=eyJjb21tYW5kIjoibnB4IG1jcC1yZW1vdGUgaHR0cHM6Ly9tY3AuY2lhbmZyYW5pLmRldi9tY3AifQ%3D%3D)
### Claude Desktop
```json
{
"rules": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.cianfrani.dev/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.
## Resources
- [Deploying this shit on netlify](https://developers.netlify.com/guides/write-mcps-on-netlify/)
## Dev
1. Start the server
```
npm run dev
```
2. Open MCP inspector
```
npm run inspect
```