ZephyrDeng/dev-context
If you are the rightful owner of dev-context and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Frontend News MCP is a production-ready Model Context Protocol server designed to provide real-time aggregation and analysis of frontend development news.
Frontend News MCP - Real-time Query System
A production-ready MCP (Model Context Protocol) server providing real-time frontend development news aggregation and analysis.
Built using Claude Code PM system for spec-driven development with complete GitHub Issues traceability from requirements to production code.
š Features
Core MCP Tools
- š° Weekly Frontend News - Curated weekly reports of frontend development news from multiple sources
- ā Trending Repositories - GitHub trending analysis for frontend technologies and frameworks
- š Technical Topic Search - Intelligent search and analysis of specific frontend technologies
Enterprise Architecture
- šļø Multi-layer Caching - High-performance Redis-backed caching with TTL and concurrency safety
- š Concurrent Data Collection - Multi-source parallel data gathering (RSS/API/HTML)
- š Smart Data Processing - Intelligent scoring, deduplication, and content formatting
- š³ Production Deployment - Docker containerization with CI/CD and monitoring
š Table of Contents
- Quick Start
- MCP Tools
- Architecture
- Development
- Deployment
- API Documentation
- Project Management
- Contributing
š Quick Start
Using Docker (Recommended)
# Clone the repository
git clone https://github.com/ZephyrDeng/dev-context.git
cd dev-context
# Start with Docker Compose
docker-compose up -d
# Check status
docker-compose ps
Local Development
# Navigate to the MCP server code
cd /Users/zephyr/mcp-servers/epic-mvp
# Install dependencies
go mod tidy
# Run locally
make run-dev
# Or build and run
make build
./bin/github.com/ZephyrDeng/dev-context
š MCP Tools
1. Weekly Frontend News (weekly_news
)
Aggregates and curates frontend development news from multiple sources.
Parameters:
startDate
- Start date for news collection (optional, defaults to 7 days ago)endDate
- End date (optional, defaults to today)category
- Filter by technology (react, vue, angular, etc.)minQuality
- Minimum quality score (0.0-1.0, default 0.5)maxResults
- Maximum results (default 50, max 200)
Example Usage:
{
"name": "weekly_news",
"arguments": {
"category": "react",
"minQuality": 0.7,
"maxResults": 30
}
}
2. Trending Repositories (trending_repos
)
Analyzes GitHub trending repositories for frontend technologies.
Parameters:
language
- Programming language filter (javascript, typescript, etc.)timeRange
- Time range (daily, weekly, monthly)minStars
- Minimum star count (default 10)maxResults
- Maximum results (default 30, max 100)
Example Usage:
{
"name": "trending_repos",
"arguments": {
"language": "typescript",
"timeRange": "weekly",
"minStars": 100
}
}
3. Technical Topic Search (topic_search
)
Intelligent search and analysis of specific frontend technologies.
Parameters:
topic
- Technology or topic to searchsources
- Comma-separated list of sourcesdepth
- Search depth (shallow, moderate, deep)maxResults
- Maximum results (default 20, max 100)
Example Usage:
{
"name": "topic_search",
"arguments": {
"topic": "Next.js 15",
"depth": "moderate",
"maxResults": 25
}
}
š Architecture
System Components
Frontend News MCP Server
āāā š MCP Protocol Layer (Go SDK v0.4.0)
āāā š ļø Core Tools
ā āāā weekly_news # Frontend news aggregation
ā āāā trending_repos # GitHub trending analysis
ā āāā topic_search # Technical topic search
āāā š Data Processing
ā āāā Multi-source collection (RSS/API/HTML)
ā āāā Content processing & scoring
ā āāā Format conversion (JSON/Markdown/Text)
āāā š¾ Caching Layer
ā āāā Redis backend
ā āāā TTL management
ā āāā Concurrency safety
āāā š Deployment
āāā Docker containers
āāā CI/CD pipeline
āāā Monitoring & logs
Data Sources
- GitHub API - Repository trends and statistics
- Dev.to API - Developer community articles
- RSS Feeds - CSS-Tricks, Hacker News, etc.
- Web Scraping - Additional frontend resources
š» Development
Prerequisites
- Go 1.21+
- Docker & Docker Compose
- GitHub CLI (for project management)
Build Commands
# Development build
make build-dev
# Production build
make build-prod
# Cross-platform builds
make build-all
# Run tests
make test
# Test coverage
make test-coverage
# Docker build
make docker-build
Testing
The project includes comprehensive testing with >80% coverage:
# Run all tests
make test
# Integration tests
make test-integration
# MCP protocol tests
make test-mcp
# View coverage report
open coverage/coverage.html
š Deployment
Production Deployment
# Build production image
make docker-build
# Deploy with monitoring
docker-compose -f docker-compose.prod.yml up -d
# Check health
curl http://localhost:8080/health
Environment Configuration
Key environment variables:
# Server Configuration
MCP_SERVER_HOST=0.0.0.0
MCP_SERVER_PORT=8080
# Cache Configuration
REDIS_URL=redis://localhost:6379
# API Keys (store securely)
GITHUB_TOKEN=your_github_token
DEV_TO_API_KEY=your_dev_to_key
See for detailed deployment instructions.
š API Documentation
- - Complete MCP tools documentation
- - Step-by-step setup instructions
- - Common issues and solutions
š Project Management
This project was built using the Claude Code PM system for spec-driven development:
Development Workflow
- ā PRD Creation - Comprehensive product requirements
- ā Epic Planning - Technical architecture and approach
- ā Task Decomposition - Granular implementation tasks
- ā GitHub Integration - Full issue tracking and traceability
- ā Parallel Execution - Multiple concurrent development streams
Project Status
- š Epic MVP Completed - 100% (8/8 tasks)
- ā MCP SDK Integration
- ā Multi-source Data Collection
- ā Cache Management System
- ā Core MCP Tools Implementation
- ā Data Processing & Formatting
- ā Complete Test Suite (>80% coverage)
- ā Production Deployment & Documentation
Project Management Commands
# View project status
/pm:status
# Sync with GitHub Issues
/pm:sync
# View all completed work
/pm:epic-show mvp
š¤ Contributing
- Fork the repository
- Create a feature branch:
git checkout -b feature/amazing-feature
- Make your changes
- Run tests:
make test
- Commit changes:
git commit -m 'Add amazing feature'
- Push to branch:
git push origin feature/amazing-feature
- Open a Pull Request
š Project Metrics
- Lines of Code: 15,000+
- Test Coverage: >80%
- Build Time: <2 minutes
- Docker Image: <50MB (Alpine-based)
- Startup Time: <5 seconds
š License
This project is licensed under the MIT License - see the file for details.
šÆ Roadmap
- Additional data sources integration
- Advanced filtering and personalization
- GraphQL API support
- WebSocket real-time updates
- Mobile-optimized responses
Built with Claude Code using spec-driven development and GitHub Issues project management.
ā Star History
If this project helps you, please consider giving it a star!