How quantgeekdev/mcp-framework works
Main Components
a) Core Framework Components:
• MCPServer (central component)
• Feature Loaders (PromptLoader, ResourceLoader, ToolLoader)
• Base Classes (BaseTool, BasePrompt, BaseResource)
• CLI Interface
b) External Integration Points:
• Claude Desktop Integration
• LLM (Language Model) Interface
• Client Applications
Component Relationships
• Inheritance relationships (Base classes → Implementations)
• Data flow (Client requests → Server → Tools/Prompts/Resources)
• Loading/Discovery paths (Loaders → Implementation directories)
Specific Elements
a) Framework Core:
┌─ MCPServer
• Feature Loaders
• PromptLoader
• ResourceLoader
• ToolLoader
• Logger
b) Base Classes:
┌─ Abstract Components
• BaseTool
• BasePrompt
• BaseResource
c) CLI Structure:
┌─ CLI
• Project Creation
• Tool Addition
• Prompt Addition
• Resource Addition
Implementation Details
How the framework handles:
• Type safety with Zod integration
• Directory-based discovery system
• Runtime validation flow
• Tool/Prompt/Resource registration process
Notes for Implementation
• Use double lines for data flow paths
Additional Details
• How the CLI interfaces with the project structure
• Where user customization points exist
• Relationship with Claude Desktop
• Build pipeline flow