Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirAn intelligent MCP (Model Context Protocol) server that provides design pattern recommendations using hybrid search (semantic + keyword + graph augmentation). Access 710 design patterns across 90+ categories through a natural language interface with advanced blended RAG architecture.
# 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
Configure in your MCP client (Claude Desktop, Cursor, etc.) and start discovering patterns through natural language queries.
bun install only). The lockfile is bun.lock..git directory into dist/data (or ship it inside dist/). That path must remain a plain data directory to avoid multi‑gigabyte images and metadata leakage.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
Ask natural language questions through your MCP client:
"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
bun install
bun run build
bun run db:setup
The prepare script in package.json requires bun. If you don't have bun installed, use --ignore-scripts to skip it and build manually:
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
Add to your MCP client configuration (Claude Desktop, Cursor, etc.):
{
"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"
}
}
}
}
Important: Use absolute paths for both
argsandDATABASE_PATH. MCP clients like Cursor do not reliably support thecwdfield, so relative paths resolve against the user's home directory rather than the project directory. See the project quickstart for client-specific configuration examples.
# 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-mcp
docker compose up --build -d
GET /health - Health checkPOST /mcp - MCP JSON-RPC endpoint# 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
The project includes 654 test cases across 77 test files with 100% pass rate (0 failures, 0 skips):
# 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
This project implements the patterns it documents:
The server uses sql.js (SQLite WASM) with in-memory cosine similarity over stored embeddings. Native sqlite-vec (vec0 virtual tables) is not available in this runtime. Semantic search works for the current catalog size (~710 patterns) but does not use indexed native vector tables.
Enable LLM enrichment only when you have a real provider integration — built-in LLM bridge providers return placeholders unless extended.
Contributions are welcome! See the contributing guide.
0.7.1 → 0.7.2 across active source and documentation files.package.json, src/mcp-server.ts (Server registration + runtime info), AGENTS.md, CLAUDE.md (canonical-identity header), README.md (badge, release-notes section, version footer), CHANGELOG.md (new entry). docs/IMPROVEMENTS_03.md and QUICKSTART.md audit-evidence references preserved untouched per state #45.AGENTS.md and CLAUDE.md header (version 0.6.0) → (version 0.7.2) (was 7 minor versions behind the actual package.json).0.7.2 to MCP clients via Server constructor and /info endpoint.data/.git leak introduced by db:setup pipeline (data-hygiene test).search_type is silently ignored by validateSearchPatternsArgs and the canonical default hybrid strategy is applied.
tests/unit/input-validation.test.tstests/unit/mcp-server-search.test.tsHealthStatus import in src/mcp/http-transport.ts.eslint-disable for require-await on the synchronous check() in src/health/embedding-coverage-health-check.ts (interface conformance preserved).ensureBM25() in src/handlers/keyword-search-handler.ts to return BM25Scorer, eliminating 4 non-null assertions at the call sites.results.find() in tests/unit/bm25-scorer.test.ts with explicit toBeDefined guards.bun run typecheck clean.docs/01_Agentic_Design_Patterns.md and docs/02_Data_Engineering_Design_Patterns.md:
MIT License - see LICENSE for details.
Version: 0.7.2 Last Updated: August 2026 Patterns: 710 JSON definitions (highlight: Feature Flag / Feature Toggle) Tests: 654 test cases | 100% pass rate (0 failures, 0 skips)
See also: the latest adversarial quality assurance report (16 findings: 1 critical, 9 high-priority, 6 minor). Findings cover search pipeline correctness, configuration drift, transport security, and documentation sync.
MCP Server for suggestion of Design Patterns - Provides semantic search and recommendations for software design patterns
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Design Patterns roda localmente via stdio.
Última verificação: 2026-10-27. MCP Server for suggestion of Design Patterns - Provides semantic search and recommendations for software design patterns