create_patternsLABSCO SUMMARY
Your conventions, available to the model before it writes.
Instead of restating house style in every prompt, the style lives in a file the assistant can search - so new code and refactors come back matching patterns you already approved rather than the model's defaults.
What it is
A store of your own coding patterns held as newline-delimited JSON. Each pattern carries a name, a category, a description, the situations it suits, the technologies it applies to and code examples keyed by language - and the assistant reads them before it writes.
What you get
- Patterns created in bulk against a fixed schema: category, description, when to use it, technologies, and examples
- The whole pattern set read back, or a single pattern opened by name
- Search across the set by technology, use case or style, so the right pattern is found rather than recalled
- Further code examples added to a pattern that already exists, so one pattern can carry several languages
- Patterns and individual examples deleted when they stop reflecting how you write
Requirements
An MCP client, and somewhere to keep the store: patterns are written as newline-delimited JSON, one object per line, so the file can be read, diffed and committed alongside the code it describes. No account and no key.
Setup effort
Build from source — git clone https://github.com/nicholasrubright/mcpatterns.git
USE CASES
Getting generated code in your house style
Search the store for the pattern that fits the task and have it read before any code is written.
Writing a convention down once
Record the pattern with its category, its technologies and a worked example, so the next session does not have to infer it from the codebase.
Carrying a pattern into a second language
Add another example to the pattern that already exists rather than creating a near-duplicate beside it.
Refactoring toward something you already decided
Open the pattern by name and refactor against it, so the change lands on the agreed shape.
Retiring a convention you have moved on from
Delete the pattern, or just the example that no longer compiles, so the store stops teaching something you abandoned.
7 tools
Listed in project docs. Your client may show a different list.
add_code_examplesdelete_patternsdelete_code_examplesread_patternssearch_patternsopen_patternsBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
git clone https://github.com/nicholasrubright/mcpatterns.git
cd mcpatterns
pnpm install
pnpm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"mcpatterns": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCPATTERNS>/dist/index.js"
]
}
}
}