Интеллектуальный MCP-сервер (Model Context Protocol), который даёт рекомендации по паттернам проектирования с помощью гибридного поиска (семантический + по ключевым словам + графовое дополнение). Доступ к 710 паттернам проектирования из 90+ категорий через интерфейс на естественном языке с продвинутой архитектурой комбинированного RAG.
# Clone and setup
git clone https://github.com/apolosan/design_patterns_mcp.git
cd design_patterns_mcp
# Install dependencies and build (using bun)
bun install
bun run db:setup
# Or using npm (if bun is not installed)
npm install --ignore-scripts
npx tsc
node dist/cli/migrate.js
node dist/cli/seed.js
node dist/cli/generate-embeddings.js
node dist/cli/setup-relationships.jsНастройте его в вашем MCP-клиенте (Claude Desktop, Cursor и т. д.) и начните находить паттерны с помощью запросов на естественном языке.
Related MCP server: Acemcp
Используйте Bun в качестве канонического пакетного менеджера для этого репозитория (только bun install). Файл блокировки — bun.lock.
Никогда не копируйте каталог .git в dist/data (и не включайте его в dist/). Этот путь должен оставаться обычным каталогом данных, чтобы избежать многогигабайтных образов и утечки метаданных.
Возможность | Описание |
Гибридный поисковый движок | Комбинированный RAG, объединяющий семантический поиск, поиск по ключевым словам (BM25) и графово-дополненный поиск |
710 паттернов | Полный каталог, охватывающий 90+ категорий, включая Feature Flag / Feature Toggle для прогрессивной поставки и экспериментов |
Интеграция с MCP | Бесшовная интеграция с Claude, Cursor и другими MCP-клиентами |
Многоуровневое кэширование | Кэш L1 в памяти + L3 на SQLite с частотой попаданий 95%+ |
Шина событий | Слабо связанное взаимодействие сервисов через pub/sub |
Телеметрия и мониторинг | Метрики производительности в реальном времени и мониторинг системы |
Архитектура SOLID | Чистая и поддерживаемая кодовая база, следующая лучшим практикам |
Готовность к продакшену | 654 теста в 77 тестовых файлах со 100% прохождением (0 ошибок, 0 пропусков) |
Категория | Количество | Примеры |
Классические паттерны GoF | 34 | Factory, Builder, Observer, Strategy, Command |
Архитектурные паттерны | 56 | MVC, Clean Architecture, Hexagonal, DDD, Feature Flag |
Микросервисы и облако | 39 | Circuit Breaker, Saga, Service Mesh |
Инженерия данных | 54 | Repository, CQRS, Event Sourcing |
AI/ML и MLOps | 46 | RAG, Fine-Tuning, Model Compression |
Паттерны React | 27 | Hooks, Server Components, Performance |
Блокчейн и Web3 | 115 | DeFi, NFTs, Smart Contracts, MEV |
Параллельность и реактивность | 45 | Producer-Consumer, Actor Model |
Безопасность | 21 | OAuth, RBAC, Zero Trust |
Функциональное программирование | 26 | Monads, Functors, Higher-Order Functions |
src/
├── adapters/ # External service adapters (LLM, embeddings)
├── cli/ # CLI commands (migrate, seed, embeddings, setup-relationships)
├── core/ # DI Container, configuration builder
├── db/ # Database migrations
├── events/ # Event bus system
├── handlers/ # MCP request handlers (hybrid search, recommendations)
├── health/ # Health check services
├── repositories/ # Data access layer
├── search/ # Hybrid search engine
├── services/ # Business services (cache, telemetry, pattern service)
├── strategies/ # Strategy pattern implementations
├── types/ # TypeScript type definitions
└── mcp-server.ts # MCP server entry point
data/
├── patterns/ # 710 JSON pattern definitions (see `feature-flag.json`)
└── design-patterns.db # SQLite database with 710 patterns and embeddingsЗадавайте вопросы на естественном языке через ваш MCP-клиент:
"I need to create complex objects with many optional configurations"
→ Builder, Abstract Factory, Factory Method
"How to handle service failures gracefully in distributed systems?"
→ Circuit Breaker, Bulkhead, Retry, Fallback
"What pattern helps with state-dependent behavior in React?"
→ State Machine, Observer, useReducer
"How to implement secure authentication and authorization?"
→ OAuth 2.0, RBAC, JWT, Zero TrustИнструмент | Описание |
| Гибридный поиск паттернов по описаниям задач |
| Поиск по ключевым словам или семантический поиск с фильтрацией |
| Подробная информация о паттерне с примерами кода |
| Статистика по доступным паттернам |
| Состояние системы и статус сервисов |
Node.js >= 18.0.0
Bun >= 1.0.0 (рекомендуется) или npm >= 8.0.0
bun install
bun run build
bun run db:setupСкрипт prepare в package.json требует bun. Если у вас не установлен bun, используйте --ignore-scripts, чтобы пропустить его, и соберите вручную:
npm install --ignore-scripts
npx tsc
# Setup database
node dist/cli/migrate.js
node dist/cli/seed.js
node dist/cli/generate-embeddings.js
node dist/cli/setup-relationships.jsДобавьте в конфигурацию вашего MCP-клиента (Claude Desktop, Cursor и т. д.):
{
"mcpServers": {
"design-patterns": {
"command": "node",
"args": ["/absolute/path/to/design-patterns-mcp/dist/mcp-server.js"],
"env": {
"LOG_LEVEL": "info",
"DATABASE_PATH": "/absolute/path/to/design-patterns-mcp/data/design-patterns.db",
"ENABLE_HYBRID_SEARCH": "true",
"ENABLE_GRAPH_AUGMENTATION": "true",
"EMBEDDING_COMPRESSION": "true",
"ENABLE_FUZZY_LOGIC": "true",
"ENABLE_TELEMETRY": "true",
"ENABLE_MULTI_LEVEL_CACHE": "true"
}
}
}
}Важно: Используйте абсолютные пути как для
args, так и дляDATABASE_PATH. MCP-клиенты, такие как Cursor, недостаточно надёжно поддерживают полеcwd, поэтому относительные пути разрешаются относительно домашнего каталога пользователя, а не каталога проекта. Примеры конфигурации для конкретных клиентов см. в кратком руководстве проекта.
Переменная | По умолчанию | Описание |
|
| Уровень логирования (debug, info, warn, error) |
|
| Путь к базе данных SQLite |
|
| Включить комбинированный поиск RAG |
|
| Включить обход связей между паттернами |
|
| Снижение размерности |
|
| Уточнение результатов с помощью нечёткой логики |
|
| Метрики производительности |
|
| Кэширование L1 + L3 |
|
| Лимит параллельных запросов |
|
| Максимальный размер кэша |
|
| TTL кэша в миллисекундах |
|
| Режим транспорта (stdio/http) |
|
| HTTP-порт (режим http) |
|
| Путь к конечной точке MCP |
|
| Путь проверки состояния |
|
| Пропустить настройку базы данных |
# Build
docker build -t design-patterns-mcp .
# Run HTTP mode
docker run -p 3000:3000 -e TRANSPORT_MODE=http design-patterns-mcp
# Run stdio mode (default)
docker run design-patterns-mcpdocker compose up --build -dПеременная | По умолчанию | Описание |
|
| Режим транспорта (stdio/http) |
|
| HTTP-порт (режим http) |
|
| Путь к конечной точке MCP |
|
| Путь проверки состояния |
|
| Путь к базе данных SQLite |
|
| Уровень логирования |
|
| Пропустить настройку базы данных |
GET /health — проверка состояния
POST /mcp — конечная точка MCP JSON-RPC
# Development
bun run build # Compile TypeScript
bun run dev # Development with hot reload
bun run start # Build and start production server
# Database
bun run db:setup # Complete database setup
bun run migrate # Run migrations
bun run seed # Seed pattern data
bun run generate-embeddings # Generate semantic embeddings
bun run setup-relationships # Setup pattern relationships
# Quality
bun run test # Run all tests
bun run lint # Check code quality
bun run lint:fix # Auto-fix linting issues
bun run typecheck # TypeScript type checkingПроект включает 654 теста в 77 тестовых файлах со 100% прохождением (0 ошибок, 0 пропусков):
Контрактные тесты: проверка соответствия протоколу MCP
Интеграционные тесты: тесты взаимодействия компонентов с реальной базой данных SQLite и эмбеддингами
Тесты производительности: бенчмарки поиска и векторизации
Модульные тесты: тесты отдельных компонентов
# Run all tests
bun run test
# Run specific test suites
bun run test:unit -- --grep "PatternService"
bun run test:integration -- --grep "database"
bun run test:performance -- --timeout 30000Этот проект реализует паттерны, которые он документирует:
Паттерн | Реализация |
Репозиторий |
|
Сервисный слой |
|
Пул объектов |
|
Внедрение зависимостей |
|
Стратегия |
|
Шина событий |
|
Многоуровневый кэш |
|
Строитель |
|
Сервер использует sql.js (SQLite WASM) с косинусной схожестью в памяти по сохранённым эмбеддингам. Нативный sqlite-vec (виртуальные таблицы vec0) недоступен в этой среде выполнения. Семантический поиск работает для текущего размера катал
Тестовый набор полностью подтверждён: 654/654 зелёных, 0 пропусков, 0 TODO (ранее — 651/654 с 3 флейками).
Устранена утечка data/.git, внесённая конвейером db:setup (тест data-hygiene).
Два устаревших теста приведены в соответствие с контрактом BUG-007: snake_case search_type молча игнорируется функцией validateSearchPatternsArgs, и применяется каноническая стратегия по умолчанию hybrid.
tests/unit/input-validation.test.ts
tests/unit/mcp-server-search.test.ts
В README.md исправлен дрейф версии: концевой блок теперь отражает каноническую базовую линию 0.7.0 → 0.7.1; бейдж, разделы «Production Ready» и «Testing» приведены в соответствие с текущим набором из 654 тестов.
Базовая линия линтера восстановлена: 0 ошибок, код выхода 0 (было 2 ошибки + 6 предупреждений).
Удалён неиспользуемый импорт HealthStatus в src/mcp/http-transport.ts.
Добавлен точечный eslint-disable для require-await на синхронном check() в src/health/embedding-coverage-health-check.ts (соответствие интерфейсу сохранено).
Выполнен рефакторинг ensureBM25() в src/handlers/keyword-search-handler.ts — теперь функция возвращает BM25Scorer, что устраняет 4 ненулевых утверждения (non-null assertions) в местах вызова.
Два ненулевых утверждения на results.find() в tests/unit/bm25-scorer.test.ts заменены явными защитами toBeDefined.
bun run typecheck — чисто.
Добавлено 24 новых паттерна проектирования из docs/01_Agentic_Design_Patterns.md и docs/02_Data_Engineering_Design_Patterns.md:
3 Agentic AI: Multi-Agent Collaboration, Goal Setting and Monitoring, Exception Handling and Recovery.
21 Data Engineering: Aligned Fan-In, Unaligned Fan-In, Bin Pack Orderer, Exclusive Choice, FIFO Orderer, Fine-Grained Accessor for Resources, Fine-Grained Accessor for Tables, Fine-Grained Tracker, In-Place Overwriter, Isolated Sequencer, Metadata Decorator, Metadata Enhancer, Offline Observer, Schema Compatibility Enforcer, Schema Migrator, Secretless Connector, Secrets Pointer, Single Runner, Skew Detector, SLA Misses Detector, Vertical Partitioner.
Каталог вырос с 686 до 710 паттернов (Agentic AI: 3→6, Data Engineering: 4→25).
Проверка целостности PASS: 710 паттернов, 151 валидная связь.
654/654 тестов проходят (100% зелёных, 0 пропусков, 0 TODO).
Лицензия MIT — подробнее см. LICENSE.
Заметки по векторному поиску (sql.js vs sqlite-vec) — см. руководство для контрибьюторов
Справочник по инструментальной поверхности MCP
Индекс документации
Версия: 0.7.2 Последнее обновление: Август 2026 Паттерны: 710 JSON-определений (особо выделены: Feature Flag / Feature Toggle) Тесты: 654 тестовых случая | 100% успешных (0 ошибок, 0 пропусков)
См. также: последний adversarial-отчёт по обеспечению качества (16 находок: 1 критическая, 9 высокоприоритетных, 6 незначительных). Находки охватывают корректность конвейера поиска, дрейф конфигурации, транспортную безопасность и синхронизацию документации.
Get the total number of design patterns in the database
| Name | Required | Description | Default |
|---|---|---|---|
| includeDetails | No | Include breakdown by category |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get[s] the total number', implying a read-only operation, but doesn't mention any behavioral traits such as performance considerations, error handling, or whether it's a simple count versus an aggregated query. For a tool with zero annotation coverage, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every part of the sentence earns its place by conveying essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (one optional parameter) and high schema coverage, the description is adequate but has clear gaps. It lacks output schema information, usage guidelines, and behavioral context, which could help an agent use it correctly. However, for a simple counting tool, it meets the minimum viable threshold without being fully comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the parameter 'includeDetails' clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, as it doesn't mention parameters at all. According to the rules, when schema_description_coverage is high (>80%), the baseline score is 3, which is appropriate here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('total number of design patterns in the database'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'find_patterns' or 'search_patterns', which might also retrieve pattern information, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'find_patterns', 'get_pattern_details', or 'search_patterns'. It lacks any context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Find design patterns matching a problem description using semantic search
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language description of the problem or requirements | |
| categories | No | Optional: Pattern categories to search in | |
| maxResults | No | Maximum number of recommendations to return | |
| programmingLanguage | No | Target programming language for implementation examples |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'semantic search' but doesn't explain what this entails—e.g., how results are ranked, whether it's a read-only operation, or any limitations like rate limits or authentication needs. For a tool with no annotation coverage, this leaves critical behavioral traits unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core purpose ('Find design patterns...'), making it easy to understand at a glance. Every part of the sentence earns its place by conveying essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (semantic search with 4 parameters) and the absence of both annotations and an output schema, the description is insufficient. It doesn't cover behavioral aspects like result format, error handling, or how semantic search works, nor does it explain the relationship between parameters and outcomes. This leaves significant gaps for an AI agent to use the tool effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description adds no additional meaning beyond the schema, such as explaining the 'semantic search' process in relation to the 'query' parameter or how 'categories' affect results. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Find design patterns matching a problem description using semantic search.' It specifies the verb ('Find'), resource ('design patterns'), and method ('semantic search'), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'search_patterns' or 'count_patterns,' which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_patterns' and 'count_patterns' available, it fails to indicate scenarios where this tool is preferred, such as for semantic versus keyword-based searches, or how it differs from 'get_pattern_details.' This lack of comparative context leaves the agent without clear usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get detailed information about a specific pattern
| Name | Required | Description | Default |
|---|---|---|---|
| patternId | Yes | Pattern ID to get details for |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states it 'gets' information, implying a read-only operation, but doesn't disclose any behavioral traits such as error handling, permissions needed, rate limits, or what 'detailed information' includes. This is a significant gap for a tool with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' entails, potential return values, or any behavioral context. For a tool with no structured data beyond the input schema, this leaves significant gaps in understanding its full functionality.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the parameter 'patternId' clearly documented. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'detailed information about a specific pattern', which is specific and understandable. However, it doesn't differentiate from sibling tools like 'find_patterns' or 'search_patterns' that might also retrieve pattern information, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'find_patterns' or 'search_patterns'. It lacks context about whether this is for retrieving details of a known pattern ID versus searching for patterns, leaving usage unclear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search patterns by keyword or semantic similarity
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| searchType | No | hybrid | |
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions search functionality but fails to describe critical behaviors such as pagination, rate limits, authentication needs, or what happens on no matches. For a search tool with zero annotation coverage, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at one sentence with zero waste, front-loading the core functionality. Every word earns its place, making it easy for an agent to parse quickly without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity as a search function with 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on return values, error handling, and behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond basic invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low at 33%, with only the 'query' parameter documented. The description adds value by explaining that searches can be by keyword or semantic similarity, which helps interpret the 'searchType' enum, but it doesn't clarify the 'limit' parameter or provide details beyond what the schema implies. This partial compensation justifies a baseline score.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as searching patterns using keyword or semantic similarity, which is specific and actionable. However, it doesn't explicitly distinguish this from sibling tools like 'find_patterns' or 'count_patterns', leaving some ambiguity about when to choose one over another.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like 'find_patterns' or 'count_patterns'. It mentions search methods but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
count_patternsfind_patternsget_pattern_detailssearch_patternsScored across 4 tools
Multiple tools have overlapping purposes that could cause confusion. 'find_patterns' and 'search_patterns' both appear to search for patterns, with descriptions that are nearly identical ('semantic search' vs 'keyword or semantic similarity'), making them difficult to distinguish. 'count_patterns' and 'get_pattern_details' are clearer, but the overlap between the two search tools significantly reduces disambiguation.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'count_patterns', 'find_patterns', 'get_pattern_details', and 'search_patterns'. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With only 4 tools, the set feels thin for a server focused on design patterns, which typically involve operations like creating, updating, or categorizing patterns. While basic retrieval functions are covered, the low count may limit functionality for more complex agent tasks, placing it in the borderline range for appropriateness.
The tool set is severely incomplete for a design patterns domain, as it only supports read operations (counting, searching, and getting details) with no ability to create, update, delete, or manage patterns. This lack of CRUD coverage creates significant gaps that will likely cause agent failures when trying to perform full lifecycle tasks.
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
295k+ bug-fix patterns with MCP Hub proxy, PII filtering, and code search
