MCPatterns
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATTERNS_FILE_PATH | No | Custom path for the patterns database file. Can be absolute path or relative to script directory. Defaults to patterns.json in the server directory. | patterns.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_patternsC | Create multiple new coding patterns in the database |
| add_code_examplesC | Add new code examples to existing patterns |
| delete_patternsC | Delete multiple patterns from the database |
| delete_code_examplesC | Delete specific code examples from patterns |
| read_patternsB | Read all patterns from the database |
| search_patternsC | Search for patterns based on a query across all fields |
| open_patternsC | Open specific patterns by their names |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but 'open_patterns' and 'read_patterns' could cause confusion as both involve accessing patterns, with 'open' being less clear about its specific function compared to 'read' for retrieval. The other tools clearly target different operations like creation, deletion, addition, and search.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'add_code_examples', 'create_patterns', and 'search_patterns'. This uniformity makes the tool set predictable and easy to understand at a glance.
With 7 tools, the count is well-scoped for managing coding patterns, covering core operations like create, read, search, delete, and example management. Each tool appears to serve a necessary function without being excessive or insufficient for the domain.
The tool set provides good coverage for CRUD operations on patterns and code examples, including create, read, search, and delete. However, there is a minor gap in update functionality for patterns or examples, which might require workarounds, though the domain is still largely covered.