A Universal Model Context Protocol Server for Advanced Prompt Management
Production-ready MCP server with intelligent prompt orchestration, hot-reload capabilities, and framework-driven AI workflows. Compatible with Claude Desktop, Cursor Windsurf, and any MCP client.
Quick Start β’ Features β’ Documentation β’ Configuration
Three-Tier Execution Architecture
- Prompt Execution: Lightning-fast single prompt execution with variable substitution
- Template Processing: Framework-enhanced templates with Nunjucks templating engine
- Chain Workflows: Multi-step LLM-driven workflows with state management
Intelligent System Components
- Structural Analysis: Automatic execution type detection based on file structure
- Hot-Reload System: Update prompts instantly without server restarts
- Quality Gates: Framework-aware validation with conditional logic
- Performance Monitoring: Comprehensive startup orchestration and health monitoring
Universal MCP Compatibility
- Transport Support: STDIO for desktop clients, SSE for web applications
- Client Integration: Native support for Claude Desktop, Cursor Windsurf, and custom MCP clients
- Protocol Compliance: Full Model Context Protocol implementation with tool registration
Manage AI capabilities directly within conversations through three consolidated MCP tools:
# Universal prompt execution with intelligent type detection
prompt_engine >>code_formatter language="Python" style="PEP8"
# Create and manage prompts with intelligent analysis
prompt_manager create name="code_reviewer" type="template" \
content="Analyze {{code}} for security, performance, and maintainability"
# Analyze existing prompts for execution optimization
prompt_manager analyze_type prompt_id="my_prompt"
# System control and framework management
system_control switch_framework framework="ReACT" reason="Problem-solving focus"
# Execute complex multi-step LLM-driven chains
prompt_engine >>code_review_optimization_chain target_code="..." language_framework="TypeScript"Key Benefits:
- Structural Intelligence: Automatic execution routing based on file structure analysis
- Dynamic Capability Building: Extend AI assistant capabilities through conversational management
- Minimal Configuration: Execution type detection requires no manual setup
- Systematic Workflow: Integrated creation, routing, and framework application
- Intelligent Command Routing: Built-in command detection with multi-strategy parsing
- Methodology Integration: Four thinking frameworks (CAGEERF, ReACT, 5W1H, SCAMPER) with conditional application
The server implements a sophisticated methodology system that applies structured thinking frameworks to AI interactions:
- CAGEERF: Comprehensive structured approach (Context, Analysis, Goals, Execution, Evaluation, Refinement, Framework)
- ReACT: Reasoning and Acting pattern for systematic problem-solving
- 5W1H: Who, What, When, Where, Why, How systematic analysis
- SCAMPER: Creative problem-solving (Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse)
- Manual Selection: Choose optimal methodology based on specific needs
- Runtime Switching: Change active framework with performance monitoring
- Conditional Application: Framework enhancement applied when beneficial
- Performance Monitoring: Track framework switching mechanics and usage
# Switch methodology for different approaches
system_control switch_framework framework="ReACT" reason="Problem-solving focus"
# Monitor framework performance and usage
system_control analytics show_details=true
# Get current framework status
system_control statusResult: Structured, systematic AI conversations through proven thinking methodologies.
Core Analysis Functions:
- Structural Analysis: Detects execution type by examining template variables (
{{variable}}), chain steps, and file structure - Framework Application: Applies selected framework methodology based on execution tier
- Routing Logic: Routes to appropriate execution tier (prompt/template/chain) based on structural characteristics
Optional Semantic Enhancement:
- LLM Integration: When enabled, provides semantic understanding of prompt content
- Advanced Analysis: Methodology recommendations and complexity assessment
- Default Mode: Structural analysis only (no LLM dependency)
Framework Control:
# Manual framework selection
system_control switch_framework framework="ReACT" reason="Problem-solving focus"- One-Command Installation: Complete setup in under 60 seconds
- Hot-Reload System: Update prompts, configs, and templates without restart
- Rich Template Engine: Nunjucks with conditionals, loops, and data injection
- Universal MCP Integration: Works with Claude Desktop, Cursor Windsurf, and any MCP client
- Multi-Transport Support: STDIO for desktop + SSE/REST for web
- Dynamic Management: Update, delete, and reload prompts on-the-fly
- Orchestrated Startup: Phased initialization with dependency management
- Error Handling: Graceful degradation with comprehensive logging
- Health Monitoring: Real-time module status, performance metrics, diagnostics
- Environment Detection: Automatic adaptation for development and production
- Modular Design: Extensible architecture for custom workflows
- Security: Input validation, sanitization, and error boundaries
- prompt_engine: Universal execution with intelligent analysis and chain coordination
- prompt_manager: Complete lifecycle management with smart filtering and gate management
- system_control: Framework management, analytics, and system administration
- Structural Type Detection: Automatic routing between prompt/template/chain execution
- Framework Integration: Four methodologies with manual selection and conditional injection
- LLM-Driven Chains: Step-by-step workflow coordination with state management
- Performance Analytics: Three-tier execution monitoring with framework switching tracking
- Smart Argument Parsing: JSON objects, single arguments, or conversational context
Get the server running in under a minute:
# Clone, install, build, and start
git clone https://github.com/minipuft/claude-prompts-mcp.git
cd claude-prompts-mcp/server && npm install && npm run build && npm startDrop this into your claude_desktop_config.json:
{
"mcpServers": {
"claude-prompts-mcp": {
"command": "node",
"args": ["E:\\path\\to\\claude-prompts-mcp\\server\\dist\\index.js"],
"env": {
"MCP_PROMPTS_CONFIG_PATH": "E:\\path\\to\\claude-prompts-mcp\\server\\prompts\\promptsConfig.json"
}
}
}
}Configure your MCP client to connect via STDIO transport:
- Command:
node - Args:
["path/to/claude-prompts-mcp/server/dist/index.js"] - Environment (Optional):
MCP_PROMPTS_CONFIG_PATH=path/to/prompts/promptsConfig.json
For Claude Code CLI users:
claude mcp add-json claude-prompts-mcp '{"type":"stdio","command":"node","args":["path/to/claude-prompts-mcp/server/dist/index.js"],"env":{}}'Start using the server immediately:
# Discover prompts with intelligent filtering
prompt_manager list filter="category:analysis"
# Execute prompts with automatic type detection
prompt_engine >>friendly_greeting name="Developer"
# Analyze content with framework enhancement
prompt_engine >>content_analysis input="research data"
# Run multi-step LLM-driven chains
prompt_engine >>code_review_optimization_chain target_code="..." language_framework="TypeScript"
# Monitor system performance
system_control analytics include_history=true
# Create new prompts conversationally
"Create a prompt called 'bug_analyzer' that finds and explains code issues"
# Refine existing prompts
"Make the bug_analyzer prompt also suggest performance improvements"
# Reference existing chain prompts
# Example chains available: code_review_optimization_chain, create_docs_chain, video_notes_enhanced
# Manual control when needed
prompt_engine >>content_analysis input="sensitive data" step_confirmation=true gate_validation=trueThe system provides a structured approach to prompt management through systematic methodology application.
The orchestration engine monitors files and reloads everything seamlessly:
# Edit any prompt file β Server detects β Reloads automatically β Zero downtime- Instant Updates: Change templates, arguments, descriptions in real-time
- Zero Restart Required: Advanced hot-reload system keeps everything running
- Smart Dependency Tracking: Only reloads what actually changed
- Graceful Error Recovery: Invalid changes don't crash the server
Nunjucks-powered dynamic prompts with full templating capabilities:
Analyze {{content}} for {% if focus_area %}{{focus_area}}{% else %}general{% endif %} insights.
{% for requirement in requirements %}
- Consider: {{requirement}}
{% endfor %}
{% if previous_context %}
Build upon: {{previous_context}}
{% endif %}- Conditional Logic: Smart prompts that adapt based on input
- Loops & Iteration: Handle arrays and complex data structures
- Template Inheritance: Reuse and extend prompt patterns
- Real-Time Processing: Templates render with live data injection
Multi-phase startup with comprehensive health monitoring:
Phase 1: Foundation β Config, logging, core services
Phase 2: Data Loading β Prompts, categories, validation
Phase 3: Module Init β Tools, executors, managers
Phase 4: Server Launch β Transport, API, diagnostics- Dependency Management: Modules start in correct order with validation
- Health Monitoring: Real-time status of all components
- Performance Metrics: Memory usage, uptime, connection tracking
- Diagnostic Tools: Built-in troubleshooting and debugging
Multi-step workflows implemented as LLM-driven instruction sequences embedded in markdown templates:
Chains are defined directly in markdown files using step headers that guide Claude through a systematic process:
# Comprehensive Code Review
## User Message Template
**Target Code**: {{target_code}}
**Language/Framework**: {{language_framework}}
This chain performs a systematic 6-step code review:
## Step 1: Structure & Organization Analysis
Analyze code architecture, organization, patterns, naming conventions...
**Output Required**: Structural assessment with identified patterns.
---
## Step 2: Functionality & Logic Review
Examine business logic correctness, edge cases, error handling...
**Output Required**: Logic validation with edge case analysis.
---
## Step 3: Security & Best Practices Audit
Review for security vulnerabilities: input validation, authentication...
**Output Required**: Security assessment with vulnerability identification.Key Features:
- LLM-Driven Execution: Claude follows step-by-step instructions embedded in the template
- Context Preservation: Each step builds on previous outputs naturally
- Flexible Structure: Steps can include conditional logic and branching
- Framework Integration: Automatically enhanced with active methodology (CAGEERF/ReACT)
For chains that orchestrate multiple reusable prompts, use the markdown-embedded format:
## Chain Steps
1. promptId: extract_key_points
stepName: Extract Key Points
inputMapping:
content: original_content
outputMapping:
key_points: extracted_points
2. promptId: sentiment_analysis
stepName: Analyze Sentiment
inputMapping:
text: extracted_points
outputMapping:
sentiment: analysis_resultCapabilities:
- Prompt Reuse: Chain together existing prompts
- Data Flow Mapping: Explicit input/output variable mapping
- Gate Integration: Apply quality gates at each step
- Error Recovery: Graceful handling of failed steps
Real Examples: See working chain implementations:
server/prompts/development/code_review_optimization_chain.md- 6-step code review workflowserver/prompts/documentation/create_docs_chain.md- Documentation generation chainserver/prompts/content_processing/video_notes_enhanced.md- Video analysis workflow
graph TB
A[Claude Desktop] -->|MCP Protocol| B[Transport Layer]
B --> C[π§ Orchestration Engine]
C --> D[π Prompt Manager]
C --> E[π οΈ MCP Tools Manager]
C --> F[βοΈ Config Manager]
D --> G[π¨ Template Engine]
E --> H[π§ Management Tools]
F --> I[π₯ Hot Reload System]
style C fill:#ff6b35
style D fill:#00ff88
style E fill:#0066cc
This server implements the Model Context Protocol (MCP) standard and works with any compatible client:
- Claude Desktop: Full integration support
- Cursor Windsurf: Native MCP compatibility
- Claude Code: Full native support
- STDIO: Primary transport for desktop clients
- Server-Sent Events (SSE): Web-based clients and integrations
- HTTP Endpoints: Basic endpoints for health checks and data queries
- Auto-Discovery: Clients detect tools automatically
- Tool Registration: Dynamic capability announcement
- Hot Reload: Changes appear instantly in clients
- Error Handling: Graceful degradation across clients
Note: As MCP adoption grows, this server will work with any new MCP-compatible AI assistant or development environment without modification.
Fine-tune your server's behavior:
{
"server": {
"name": "Claude Custom Prompts MCP Server",
"version": "1.0.0",
"port": 9090
},
"prompts": {
"file": "promptsConfig.json",
"registrationMode": "name"
},
"transports": {
"default": "stdio",
"sse": { "enabled": false },
"stdio": { "enabled": true }
}
}Structure your AI command library:
{
"categories": [
{
"id": "development",
"name": "π§ Development",
"description": "Code review, debugging, and development workflows"
},
{
"id": "analysis",
"name": "π Analysis",
"description": "Content analysis and research prompts"
},
{
"id": "creative",
"name": "π¨ Creative",
"description": "Content creation and creative writing"
}
],
"imports": [
"prompts/development/prompts.json",
"prompts/analysis/prompts.json",
"prompts/creative/prompts.json"
]
}Build sophisticated AI workflows using two complementary approaches:
The primary method uses step-by-step instructions embedded directly in markdown templates. Claude executes each step systematically while maintaining context:
# Research Analysis Chain
## User Message Template
Research {{topic}} and provide {{analysis_type}} analysis.
## Step 1: Initial Research
Gather comprehensive information about {{topic}} from available sources.
Focus on {{analysis_type}} perspectives.
**Output Required**: Research summary with key findings.
---
## Step 2: Extract Key Insights
From the research findings, identify the most relevant insights.
Organize by importance and relevance to {{analysis_type}} analysis.
**Output Required**: Prioritized list of insights with supporting evidence.
---
## Step 3: Analyze Patterns
Examine the extracted insights for patterns, trends, and relationships.
Consider multiple analytical frameworks.
**Output Required**: Pattern analysis with framework comparisons.
---
## Step 4: Synthesize Report
Create comprehensive report combining all findings.
**Output Required**: Structured report with executive summary.Benefits:
- Natural Flow: Claude maintains context automatically across steps
- Flexible Logic: Steps can include conditional branching and decision points
- Framework Enhanced: Automatically augmented with active methodology (CAGEERF/ReACT)
- Clear Outputs: Each step specifies required deliverables
For orchestrating multiple reusable prompts with explicit data flow:
## Chain Steps
1. promptId: research_topic
stepName: Initial Research
inputMapping:
query: topic
outputMapping:
findings: research_data
2. promptId: extract_insights
stepName: Extract Key Insights
inputMapping:
content: research_data
outputMapping:
insights: key_findings
3. promptId: analyze_patterns
stepName: Analyze Patterns
inputMapping:
data: key_findings
outputMapping:
analysis: pattern_results
4. promptId: generate_report
stepName: Synthesize Report
inputMapping:
insights: key_findings
patterns: pattern_results
outputMapping:
report: final_outputCapabilities:
- Prompt Reuse: Leverage existing prompts as chain building blocks
- Explicit Data Flow: Clear input/output mapping between steps
- Error Recovery: Graceful handling of failed steps with retry logic
- Gate Validation: Apply quality gates at each step for validation
Real Examples: View production chain implementations:
server/prompts/content_processing/noteIntegration.md- Note processing with modular steps- Review the
## Chain Stepssection in any chain prompt for complete syntax
Leverage the full power of Nunjucks templating:
# {{ title | title }} Analysis
## Context
{% if previous_analysis %}
Building upon previous analysis: {{ previous_analysis | summary }}
{% endif %}
## Requirements
{% for req in requirements %}
{{loop.index}}. **{{req.priority | upper}}**: {{req.description}}
{% if req.examples %}
Examples: {% for ex in req.examples %}{{ex}}{% if not loop.last %}, {% endif %}{% endfor %}
{% endif %}
{% endfor %}
## Focus Areas
{% set focus_areas = focus.split(',') %}
{% for area in focus_areas %}
- {{ area | trim | title }}
{% endfor %}Template Features:
- Filters & Functions: Transform data on-the-fly
- Conditional Logic: Smart branching based on input
- Loops & Iteration: Handle complex data structures
- Template Inheritance: Build reusable prompt components
Manage your prompts dynamically while the server runs:
# Update prompts with intelligent re-analysis
prompt_manager update id="analysis_prompt" content="new template"
# Modify specific sections with validation
prompt_manager modify id="research" section="examples" content="new examples"
# Hot-reload with comprehensive validation
system_control reload reason="updated templates"Management Capabilities:
- Live Updates: Change prompts without server restart
- Section Editing: Modify specific parts of prompts
- Bulk Operations: Update multiple prompts at once
- Rollback Support: Undo changes when things go wrong
Enterprise-grade observability:
Built-in monitoring and diagnostics for production environments:
// Health Check Response
{
healthy: true,
modules: {
foundation: true,
dataLoaded: true,
modulesInitialized: true,
serverRunning: true
},
performance: {
uptime: 86400,
memoryUsage: { rss: 45.2, heapUsed: 23.1 },
promptsLoaded: 127,
categoriesLoaded: 8
}
}Monitoring Features:
- Real-Time Health Checks: All modules continuously monitored
- Performance Metrics: Memory, uptime, connection tracking
- Diagnostic Tools: Comprehensive troubleshooting information
- Error Tracking: Graceful error handling with detailed logging
| Guide | Description |
|---|---|
| Installation Guide | Complete setup walkthrough with troubleshooting |
| Troubleshooting Guide | Common issues, diagnostic tools, and solutions |
| Architecture Overview | Deep dive into the orchestration engine, modules, and data flow |
| Prompt Format Guide | Master prompt creation including chain workflows |
| Prompt Management | Dynamic management and hot-reload features |
| MCP Tools Reference | Complete MCP tools documentation |
| Roadmap & TODO | Planned features and development roadmap |
| Contributing | Join our development community |
Join our development community:
- Found a bug? Open an issue
- Have an idea? Start a discussion
- Want to contribute? Check our Contributing Guide
- Need help? Visit our Documentation
Released under the MIT License - see the file for details.
Star this repo if it's improving your AI workflow
Report Bug β’ Request Feature β’ View Docs
Built for the AI development community
