spatiummeum/MCP-Server-Project-Management-Platform
If you are the rightful owner of MCP-Server-Project-Management-Platform 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 MCP Context Server is a comprehensive project management platform designed to enhance development workflows by providing persistent project context and advanced management tools.
store_context
Store project context
get_context
Retrieve project context
store_conversation
Store conversation history
get_conversation_history
Retrieve conversation history
MCP Context Server - Complete Project Management Platform
π Transform your development workflow with enterprise-grade project context management!
A comprehensive Model Context Protocol (MCP) server that revolutionizes how AI-powered editors like Cursor maintain persistent memory about development projects. This platform serves as an intelligent bridge between your development environment and a robust PostgreSQL database, enabling seamless storage and retrieval of project context, conversation history, and complete project management data.
π― What Makes This Special?
Unlike basic context storage solutions, this MCP server provides a complete enterprise project management ecosystem that grows with your development needs:
- π§ Persistent AI Memory - Never lose context across coding sessions
- π Enterprise Project Management - Complete task, user, and dependency tracking
- π Security & Compliance - Full audit trails and access control
- β‘ High Performance - Optimized PostgreSQL with connection pooling
- π§ Developer-First - Built by developers, for developers
π Perfect For:
- Solo Developers seeking better project organization
- Development Teams requiring collaboration tools
- Enterprise Projects needing compliance and auditing
- AI-Enhanced Workflows leveraging persistent context
- Complex Codebases requiring architectural tracking
π Features
From basic context storage to enterprise project management - everything you need in one powerful platform.
π Core Context & Conversations
Transform how AI remembers your project with intelligent, persistent storage:
- π§ Persistent Project Context - Maintain AI awareness across sessions
- π¬ Complete Conversation History - Never lose important discussions
- ποΈ Flexible JSONB Metadata - Extensible data structure for any use case
- β‘ Real-time Context Retrieval - Instant access to project knowledge
- π Smart Search & Filtering - Find exactly what you need, when you need it
π Extended Project Management
π File Management & Versioning
Professional-grade version control and file tracking:
- π Complete Version History - Track every change with detailed metadata
- π File Integrity Verification - SHA-256 checksums for data reliability
- π Detailed File Metadata - Size, type, language, line count, and authorship
- π― Binary & Generated File Support - Handle all file types intelligently
- π Temporal File Analysis - Understand how your codebase evolves over time
π₯ User & Role Management
Enterprise-ready team collaboration:
- π Multi-user System - Support unlimited team members
- π Granular Role System - Admin, Developer, Viewer, Tester roles
- π€ Per-user Activity Tracking - Monitor individual contributions
- π€ Team Collaboration Features - Streamlined workflow management
- π Permission-based Access Control - Secure, role-based data access
π Task & Issue Management
Complete project tracking system:
- π« Comprehensive Ticket System - Features, bugs, enhancements, documentation
- βοΈ Configurable Workflows - Customize statuses and priorities
- π Progress Tracking - Visual progress monitoring
- π¨βπ» Assignment Management - Clear responsibility delegation
- π Analytics Dashboard - Track team productivity and project health
π¦ Dependency Management
Never lose track of your project's ecosystem:
- π Universal Package Tracking - npm, pip, maven, gradle, composer, cargo support
- π License Information - Compliance and legal tracking
- π·οΈ Version Management - Production vs development dependencies
- π Dependency Analysis - Understand your project's external requirements
- β οΈ Security Monitoring - Track potential vulnerabilities
π Environment Configuration
Secure, organized configuration management:
- ποΈ Multi-environment Support - Dev, staging, production configurations
- π Sensitive Data Protection - Encrypted storage for secrets
- βοΈ Configuration Versioning - Track changes across environments
- π Environment Synchronization - Ensure consistency across stages
- π Configuration Templates - Standardize environment setups
π Activity Logs & Auditing
Enterprise-grade audit trails:
- π Complete Activity Logging - Every action is recorded
- π IP & User-Agent Tracking - Security monitoring and compliance
- π Structured Analytics - Transform logs into insights
- π Advanced Filtering - Find specific activities quickly
- π¨ Security Alerting - Monitor for suspicious activities
π¨ Builds & CI/CD
Comprehensive build and deployment tracking:
- ποΈ Build History Management - Track every build across branches
- β Automated Test Results - Integrate with your testing pipeline
- π¦ Artifact Storage Info - Keep track of build outputs
- π Deployment Tracking - Monitor releases and rollbacks
- π Build Analytics - Optimize your CI/CD performance
π Documentation System
Organized, versioned documentation management:
- π Document Type Organization - API docs, user guides, technical specs
- π Version Control - Track documentation evolution
- π·οΈ Tagging & Categorization - Organize content effectively
- π Public/Private Documentation - Control visibility appropriately
- π Full-text Search - Find information instantly
π Component Architecture
Map and understand your system's structure:
- πΊοΈ System Component Mapping - Visualize your architecture
- π Relationship Tracking - Dependencies, implementations, extensions
- π Dependency Analysis - Understand component interactions
- π¨ Architecture Visualization - Generate system diagrams
- π Impact Analysis - Understand change implications
π System Statistics
Enterprise-scale capabilities built for modern development teams.
- ποΈ 13 Optimized Database Tables - Engineered for performance and scalability
- π§ 26 Powerful MCP Tools - From basic context (4) to advanced management (22)
- π 30+ API Endpoints - Complete project management functionality
- β‘ High-Performance Architecture - Connection pooling, strategic indexing
- π Enterprise Security - Role-based access, audit trails, data integrity
- π Scalable Design - Handle projects from solo to enterprise scale
π― By the Numbers:
- 11 Extended Tables for comprehensive project management
- 22 New MCP Tools beyond basic context storage
- 6 Package Managers supported (npm, pip, maven, gradle, composer, cargo)
- 4 User Roles with granular permissions
- 4 Environment Types (dev, staging, production, testing)
- Multiple Build Types (CI, manual, release)
π Installation & Setup
Get up and running in under 5 minutes with our streamlined setup process.
π Prerequisites
Ensure you have these installed before starting:
- Node.js 22.x or higher
- Docker and Docker Compose
- Git for version control
- 4GB RAM minimum (8GB recommended for development)
- 2GB free disk space for Docker containers and data
β‘ Quick Start
π― Complete setup in 4 simple steps:
1. Clone and Navigate
git clone https://github.com/spatiummeum/MCP-Server-Project-Management-Platform.git
cd mcp-context-server
2. Environment Configuration
# Copy the example environment file
cp .env.example .env
# Edit with your preferred settings (optional - defaults work great!)
nano .env # or your preferred editor
3. Start Infrastructure
# Launch PostgreSQL, pgAdmin, and Grafana
docker compose -f docker/docker-compose.yml up -d
# Verify services are running
docker compose -f docker/docker-compose.yml ps
4. Install Dependencies & Start
# Install Node.js dependencies
cd mcp-server
npm install
# Start the MCP server
npm start
π That's it! Your MCP Context Server is now running and ready to use.
π§ Configuration Options
Environment Variables
Customize your installation with these key variables:
# Database Configuration
DB_HOST=localhost # Database host
DB_PORT=5433 # Database port (avoid conflicts with local PostgreSQL)
DB_NAME=mcp_context # Database name
DB_USER=mcp_user # Database username
DB_PASSWORD=mcp_secure_password # Database password (change in production!)
# Optional: Server Configuration
MCP_SERVER_PORT=3001 # MCP server port
NODE_ENV=development # Environment mode
LOG_LEVEL=info # Logging level
# Optional: Security (recommended for production)
SESSION_SECRET=your_session_secret_here
JWT_SECRET=your_jwt_secret_here
π Production Security Notes:
- Change default passwords in production
- Use strong secrets for JWT and sessions
- Enable SSL/TLS for database connections
- Restrict database access to application only
π Verification & Testing
Quick Health Check:
# Check all services are healthy
docker compose -f docker/docker-compose.yml ps
# Test database connectivity
cd mcp-server && npm run test-db # (if available)
# Run demo to verify functionality
node scripts/demo-extended-functionality.js
Access Admin Interfaces:
- ποΈ pgAdmin: http://localhost:5050 ( / admin)
- π Grafana: http://localhost:3000 (admin / admin)
- β‘ MCP Server: Running on port 3001
π Troubleshooting
Common Issues:
Port Conflicts:
# Check what's using port 5433
lsof -i :5433
# Or change port in docker-compose.yml
Docker Issues:
# Reset Docker environment
docker compose -f docker/docker-compose.yml down -v
docker compose -f docker/docker-compose.yml up -d
Permission Issues:
# Fix Docker permissions (Linux/macOS)
sudo chown -R $USER:$USER .
Database Connection:
# Verify database is accessible
docker exec -it mcp-postgres psql -U mcp_user -d mcp_context
π Next Steps
- π Read the
- π§ͺ Run the comprehensive demo:
node scripts/demo-extended-functionality.js
- π§ Configure your editor to use the MCP server
- π₯ Set up your first project and start tracking context!
π― Usage Examples
From basic context storage to enterprise project management - see how powerful the platform can be.
π Getting Started - Basic Context
Store and Retrieve Project Context
// Store architectural decisions
await storeContext('my-ecommerce-app', 'architecture',
'Microservices with React frontend, Node.js APIs, PostgreSQL database'
);
// Store development notes
await storeContext('my-ecommerce-app', 'dev-notes',
'Using TypeScript for type safety, Jest for testing, Docker for deployment'
);
// Retrieve context when resuming work
const architecture = await getContext('my-ecommerce-app', 'architecture');
const devNotes = await getContext('my-ecommerce-app', 'dev-notes');
console.log('Project Architecture:', architecture.content);
π Enterprise Project Management
Complete Project Overview
// Get comprehensive project status
const projectOverview = {
// Team information
team: await getProjectUsers('my-ecommerce-app'),
// Current tasks and issues
openTasks: await getProjectTasks('my-ecommerce-app', 'open'),
inProgressTasks: await getProjectTasks('my-ecommerce-app', 'in_progress'),
// Technology stack
dependencies: await getProjectDependencies('my-ecommerce-app'),
// Build and deployment info
recentBuilds: await getBuildHistory('my-ecommerce-app', null, 10),
// Documentation
docs: await getDocumentation('my-ecommerce-app'),
// Recent activity
recentActivity: await getActivityLogs('my-ecommerce-app', null, null, 20)
};
// Generate project dashboard
console.log(`
π Project: ${projectOverview.name}
π₯ Team: ${projectOverview.team.length} members
π Tasks: ${projectOverview.openTasks.length} open, ${projectOverview.inProgressTasks.length} in progress
π¦ Dependencies: ${projectOverview.dependencies.length} packages
π¨ Builds: ${projectOverview.recentBuilds.filter(b => b.status === 'success').length} successful
`);
π Security & Compliance
Activity Monitoring and Auditing
// Track sensitive operations
await logActivity('my-ecommerce-app', 'security_access', 'john.doe',
'payment-processor.js', 'modified payment logic');
await logActivity('my-ecommerce-app', 'deployment', 'admin',
'production', 'deployed v2.1.0 to production');
// Generate security audit report
const securityLogs = await getActivityLogs('my-ecommerce-app', 'security_access');
const deploymentLogs = await getActivityLogs('my-ecommerce-app', 'deployment');
// Create compliance report
const auditReport = {
period: 'Last 30 days',
securityEvents: securityLogs.length,
deployments: deploymentLogs.length,
criticalChanges: securityLogs.filter(log =>
log.details.includes('payment') || log.details.includes('auth')
)
};
π Release Management
Comprehensive Release Preparation
// Prepare release v2.1.0
const releaseVersion = 'v2.1.0';
// Store build information
await storeBuild('my-ecommerce-app', releaseVersion, 'release', 'success', {
branch: 'main',
commit: 'abc123def456',
testResults: 'All 157 tests passed',
buildTime: '4m 32s'
});
// Gather release information
const releaseInfo = {
version: releaseVersion,
// Dependencies for deployment
dependencies: await getProjectDependencies('my-ecommerce-app'),
// Test coverage and build history
buildHistory: await getBuildHistory('my-ecommerce-app', 'success', 5),
// Documentation for release notes
documentation: await getDocumentation('my-ecommerce-app', null, true),
// Team contributions
contributors: await getProjectUsers('my-ecommerce-app'),
// Recent changes
recentTasks: await getProjectTasks('my-ecommerce-app', 'closed', null, 20)
};
// Generate release checklist
console.log(`
π Release ${releaseVersion} Ready!
β
${releaseInfo.buildHistory.length} successful builds
β
${releaseInfo.dependencies.filter(d => d.type === 'production').length} production dependencies verified
β
${releaseInfo.documentation.length} documentation items updated
β
${releaseInfo.recentTasks.length} tasks completed
π₯ ${releaseInfo.contributors.length} contributors
`);
π Analytics & Insights
Development Metrics Dashboard
// Analyze team productivity
const productivityMetrics = {
// Task completion rates
tasksCompleted: await getProjectTasks('my-ecommerce-app', 'closed'),
tasksInProgress: await getProjectTasks('my-ecommerce-app', 'in_progress'),
// Build success rates
builds: await getBuildHistory('my-ecommerce-app'),
// Team activity
teamActivity: await getActivityLogs('my-ecommerce-app'),
// Documentation coverage
documentation: await getDocumentation('my-ecommerce-app')
};
// Calculate metrics
const metrics = {
taskCompletionRate: productivityMetrics.tasksCompleted.length /
(productivityMetrics.tasksCompleted.length + productivityMetrics.tasksInProgress.length),
buildSuccessRate: productivityMetrics.builds.filter(b => b.status === 'success').length /
productivityMetrics.builds.length,
dailyActivity: productivityMetrics.teamActivity.length / 30, // Last 30 days
docCoverage: productivityMetrics.documentation.length
};
console.log('π Development Metrics:', metrics);
π Advanced Use Cases
Dependency Security Analysis
// Analyze project dependencies for security
const dependencyAnalysis = {
allDeps: await getProjectDependencies('my-ecommerce-app'),
components: await getProjectComponents('my-ecommerce-app'),
relationships: await getComponentRelationships('my-ecommerce-app')
};
// Identify potential security concerns
const securityAnalysis = {
outdatedPackages: dependencyAnalysis.allDeps.filter(dep =>
dep.version.includes('beta') || dep.version.includes('alpha')
),
criticalComponents: dependencyAnalysis.components.filter(comp =>
comp.type === 'service' && comp.name.includes('auth')
),
externalDependencies: dependencyAnalysis.relationships.filter(rel =>
rel.relationship_type === 'depends_on'
)
};
π― Integration Examples
CI/CD Pipeline Integration
// Webhook from CI/CD system
async function handleBuildComplete(buildData) {
// Store build results
await storeBuild(
buildData.project,
buildData.version,
buildData.type,
buildData.status,
{
duration: buildData.duration,
testResults: buildData.tests,
coverage: buildData.coverage
}
);
// Log deployment activity
if (buildData.deployed) {
await logActivity(
buildData.project,
'deployment',
buildData.deployer,
buildData.environment,
`Deployed ${buildData.version} to ${buildData.environment}`
);
}
}
π‘ Pro Tip: Combine multiple APIs to create powerful automation workflows that keep your project data always current and actionable!
π§ͺ Testing & Demo
Explore the full capabilities with our comprehensive demo and testing suite.
π¬ Interactive Demo
Experience a complete e-commerce project simulation:
node scripts/demo-extended-functionality.js
π― What the demo showcases:
- π₯ Team Setup - 4 team members with different roles (admin, developers, tester)
- π Project Tasks - 4 realistic tasks including features and bug fixes
- π¦ Dependency Stack - 11 production and development dependencies
- π File History - Version control simulation with realistic changes
- π¨ Build Pipeline - Multiple builds with success/failure scenarios
- π Documentation - API documentation and user guides
- π Activity Tracking - Complete audit trail of all activities
π Demo Output Example:
π¬ MCP Context Server - Extended Functionality Demo
==================================================
β
Project Setup Complete: 'ecommerce-platform'
π₯ Team Members: 4 users added with roles
π Tasks Created: 4 tasks (2 features, 1 bug, 1 enhancement)
π¦ Dependencies: 11 packages tracked
π File History: 3 file versions stored
π¨ Builds: 3 builds recorded (2 success, 1 failure)
π Documentation: 2 documents created
π Activity Logs: 15+ activities recorded
π― Demo completed successfully! Check the database for all generated data.
π§ Comprehensive Testing
Run the full test suite to verify all functionality:
node scripts/test-extended-apis.js
π§ͺ Test Coverage:
- β Context Storage & Retrieval - Basic MCP functionality
- β User Management - Role-based access and permissions
- β Task Management - CRUD operations and status updates
- β Dependency Tracking - Package manager integrations
- β Environment Configuration - Secure config management
- β Activity Logging - Audit trail verification
- β Build Management - CI/CD integration testing
- β Documentation System - Version control and categorization
- β Component Architecture - Relationship mapping
- β File Metadata - Integrity and versioning
π Test Results Example:
π§ͺ MCP Context Server - Extended API Test Suite
===============================================
β
Context APIs: 4/4 tests passed
β
User Management: 6/6 tests passed
β
Task Management: 8/8 tests passed
β
Dependency Management: 5/5 tests passed
β
Environment Config: 4/4 tests passed
β
Activity Logging: 7/7 tests passed
β
Build Management: 6/6 tests passed
β
Documentation: 5/5 tests passed
β
Component Architecture: 8/8 tests passed
β
File Metadata: 4/4 tests passed
π All 57 tests passed! Your MCP server is ready for production.
π Manual Testing Guide
1. Database Verification
# Connect to PostgreSQL
docker exec -it mcp-postgres psql -U mcp_user -d mcp_context
# Check tables
\dt
# Verify data
SELECT COUNT(*) FROM project_contexts;
SELECT COUNT(*) FROM project_users;
2. API Endpoint Testing
# Test server health (if health endpoint exists)
curl http://localhost:3001/health
# Check MCP server logs
docker logs mcp-server # (if containerized)
3. Performance Testing
# Run performance benchmarks (if available)
node scripts/performance-test.js
# Monitor resource usage
docker stats
π Development Testing
Running Tests During Development:
# Install development dependencies
npm install --dev
# Run unit tests (if available)
npm test
# Run integration tests
npm run test:integration
# Run with coverage
npm run test:coverage
π§ Custom Test Scenarios
Create your own test scenarios by modifying the demo script:
// Custom test example
const customTest = async () => {
// 1. Create test project
await storeContext('test-project', 'description', 'Custom test project');
// 2. Add test data
await storeProjectUser('test-project', 'test-user', 'developer', 'Test User');
// 3. Verify data
const users = await getProjectUsers('test-project');
console.log('Test Users:', users);
// 4. Cleanup
// Add cleanup logic here
};
customTest().catch(console.error);
π Monitoring Test Results
Using Grafana for Test Monitoring:
- Access Grafana: http://localhost:3000
- Login: admin/admin
- Import Dashboard for MCP metrics
- Monitor: Query performance, connection pools, error rates
Database Performance Monitoring:
-- Check query performance
SELECT query, mean_time, calls FROM pg_stat_statements
ORDER BY mean_time DESC LIMIT 10;
-- Monitor connection usage
SELECT count(*) as connections, state FROM pg_stat_activity
GROUP BY state;
π Troubleshooting Tests
Common Test Issues:
Database Connection Errors:
# Reset database
docker compose -f docker/docker-compose.yml down -v
docker compose -f docker/docker-compose.yml up -d
Port Conflicts:
# Check port usage
netstat -tlnp | grep :5433
Permission Issues:
# Fix file permissions
chmod +x scripts/*.js
π― Next Steps After Testing
- π Review test results and understand the data structure
- π§ Configure your editor to connect to the MCP server
- π₯ Set up your team with appropriate roles
- π Start tracking your first real project
- π Monitor usage through Grafana dashboards
π‘ Pro Tip: Run the demo and tests regularly during development to ensure your customizations don't break existing functionality!
π Architecture
System Overview
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β MCP Context Server Platform β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β βββββββββββββββββββ ββββββββββββββββββββββββ βββββββββββββββββββββββββββββββ β
β β Cursor β β MCP Server β β PostgreSQL 16 β β
β β (Editor) βββββΊβ (Node.js) βββββΊβ (Docker) β β
β β β β β β β β
β β βΈ Context Req β β βΈ 26 MCP Tools β β βΈ 13 Optimized Tables β β
β β βΈ Conversations β β βΈ Connection Pool β β βΈ JSONB Metadata Fields β β
β β βΈ Real-time β β βΈ Error Handling β β βΈ ACID Transactions β β
β βββββββββββββββββββ ββββββββββββββββββββββββ βββββββββββββββββββββββββββββββ β
β β β
β ββββββββββΌβββββββββ β
β β Admin Tools β β
β β β β
β β βΈ pgAdmin :5050 β β
β β βΈ Grafana :3000 β β
β βββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Data Flow Architecture
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Data Management Layers β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β Application Layer β β
β βββββββββββββββββββ¬ββββββββββββββββββ¬ββββββββββββββββββ¬βββββββββββββββββββββββββββ€ β
β β Context API β Project API β Security API β Analytics API β β
β β β β β β β
β β βΈ store_context β βΈ store_task β βΈ log_activity β βΈ get_build_history β β
β β βΈ get_context β βΈ store_user β βΈ store_env β βΈ get_dependencies β β
β β βΈ conversations β βΈ dependencies β βΈ permissions β βΈ component_analysis β β
β βββββββββββββββββββ΄ββββββββββββββββββ΄ββββββββββββββββββ΄βββββββββββββββββββββββββββ β
β β β
β βββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββ β
β β Database Schema Layer β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€ β
β β β β
β β Core Tables (2) β Project Management (11) β β
β β βββββββββββββββββββ β βββββββββββββββββββ¬ββββββββββββββββββββββββββββββ β β
β β β project_contextsβ β β file_history β project_dependencies β β β
β β β conversation_ β β β project_users β project_environments β β β
β β β history β β β project_tasks β project_activity_logs β β β
β β βββββββββββββββββββ β β project_builds β project_documentation β β β
β β β β project_ β component_relationships β β β
β β β β components β file_metadata β β β
β β β βββββββββββββββββββ΄ββββββββββββββββββββββββββββββ β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β β
β βββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββ β
β β Infrastructure Layer β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€ β
β β β β
β β Docker Compose Environment β β
β β βββββββββββββββββββ¬ββββββββββββββββββ¬ββββββββββββββββββ¬ββββββββββββββββββ β β
β β β PostgreSQL β pgAdmin β Grafana β MCP Server β β β
β β β Port: 5433 β Port: 5050 β Port: 3000 β Port: 3001 β β β
β β β Volume: DB β Volume: Admin β Volume: Dash β Local Dev β β β
β β βββββββββββββββββββ΄ββββββββββββββββββ΄ββββββββββββββββββ΄ββββββββββββββββββ β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Feature Integration Map
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β MCP Context Server Feature Matrix β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β Development Workflow β Project Management β
β βββββββββββββββββββββββββββββββββ β ββββββββββββββββββββββββββββββββββββββββββββββ β
β β βΈ File History & Versioning β β β βΈ Task & Issue Tracking β β
β β βΈ Context Persistence β β β βΈ Team & Role Management β β
β β βΈ Conversation Memory β β β βΈ Dependency Management β β
β β βΈ Component Relationships β β β βΈ Build & CI/CD Integration β β
β βββββββββββββββββββββββββββββββββ β ββββββββββββββββββββββββββββββββββββββββββββββ β
β β β
β Security & Compliance β Analytics & Monitoring β
β βββββββββββββββββββββββββββββββββ β ββββββββββββββββββββββββββββββββββββββββββββββ β
β β βΈ Activity Auditing β β β βΈ Performance Metrics β β
β β βΈ Environment Protection β β β βΈ Usage Analytics β β
β β βΈ Access Control β β β βΈ Project Insights β β
β β βΈ Data Integrity β β β βΈ Real-time Dashboards β β
β βββββββββββββββββββββββββββββββββ β ββββββββββββββββββββββββββββββββββββββββββββββ β
β β β
β βββββββββββββββββββββββββββββββ β
β β Documentation Hub β β
β β βΈ API Reference (26 tools) β β
β β βΈ Architecture Diagrams β β
β β βΈ Integration Guides β β
β β βΈ Demo & Test Scripts β β
β βββββββββββββββββββββββββββββββ β
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
π API Reference
Core APIs (4)
store_context
- Store project contextget_context
- Retrieve project contextstore_conversation
- Store conversation historyget_conversation_history
- Retrieve conversation history
Extended APIs (22)
See for complete documentation.
File Management
store_file_history
,get_file_history
store_file_metadata
,get_file_metadata
User Management
store_project_user
,get_project_users
Task Management
store_project_task
,get_project_tasks
Dependency Management
store_project_dependency
,get_project_dependencies
Environment Configuration
store_environment_config
,get_environment_configs
Activity Logging
log_activity
,get_activity_logs
Build Management
store_build
,update_build_status
,get_build_history
Documentation
store_documentation
,get_documentation
Component Architecture
store_project_component
,store_component_relationship
get_project_components
,get_component_relationships
π Security Features
- Sensitive Configuration Protection - Marked and protected sensitive fields
- Complete Activity Auditing - Log all project activities
- IP and User-Agent Tracking - Security monitoring
- Data Integrity Checksums - File verification
- Role-based Access Control - Granular permissions
π Performance & Scalability
- Connection Pooling - Optimized PostgreSQL connections
- Strategic Indexing - Fast query performance
- JSONB Metadata - Flexible schema extension
- Structured Logging - Advanced analytics support
- Optimized Queries - Efficient data retrieval
π‘ Monitoring & Administration
The stack includes:
-
pgAdmin (http://localhost:5050) - Database administration
- Username:
admin@admin.com
- Password:
admin
- Username:
-
Grafana (http://localhost:3000) - Monitoring dashboards
- Username:
admin
- Password:
admin
- Username:
π€ Contributing
Contributions are welcomed and greatly appreciated! π
We believe in the power of community collaboration to make this project even better. Whether you're a seasoned developer or just starting out, there are many ways to contribute to the MCP Context Server project.
π Ways to Contribute
- π Bug Reports - Found a bug? Let us know!
- π‘ Feature Requests - Have an idea for improvement? Share it!
- π Documentation - Help improve our docs and examples
- π§ Code Contributions - Fix bugs, add features, or optimize performance
- π§ͺ Testing - Help us test new features and report issues
- π¨ UI/UX - Improve user experience and interfaces
- π Analytics - Add new monitoring and analytics capabilities
π Getting Started
-
Fork the repository
git fork https://github.com/your-username/mcp-context-server
-
Clone your fork
git clone https://github.com/your-username/mcp-context-server.git cd mcp-context-server
-
Create a feature branch
git checkout -b feature/amazing-feature # or git checkout -b fix/bug-description # or git checkout -b docs/improvement-description
-
Set up development environment
cp .env.example .env docker compose -f docker/docker-compose.yml up -d cd mcp-server && npm install
-
Make your changes
- Write clean, well-documented code
- Follow existing code style and conventions
- Add tests for new functionality
- Update documentation as needed
-
Test your changes
npm test node scripts/test-extended-apis.js node scripts/demo-extended-functionality.js
-
Commit your changes
git add . git commit -m "feat: add amazing new feature" # Use conventional commits: feat:, fix:, docs:, style:, refactor:, test:, chore:
-
Push to your fork
git push origin feature/amazing-feature
-
Open a Pull Request
- Provide a clear description of your changes
- Reference any related issues
- Include screenshots if applicable
- Ensure all tests pass
π Contribution Guidelines
- Code Quality - Write clean, readable, and well-documented code
- Testing - Include tests for new features and bug fixes
- Documentation - Update docs to reflect your changes
- Commit Messages - Use conventional commit format
- Pull Requests - Keep PRs focused and include clear descriptions
- Issues - Use issue templates and provide detailed information
π― Priority Areas
We're especially looking for contributions in these areas:
- π MCP Tool Integrations - New tools for different development workflows
- π Analytics Dashboard - Enhanced Grafana dashboards and metrics
- π Security Features - Advanced security and compliance tools
- β‘ Performance Optimization - Database queries and connection pooling
- π± Mobile Support - Mobile-friendly interfaces and APIs
- π Internationalization - Multi-language support
- π Integrations - GitHub, GitLab, Jira, Slack, etc.
π¬ Community & Support
- GitHub Discussions - Ask questions and share ideas
- Issues - Report bugs and request features
- Pull Requests - Submit your contributions
- Code Reviews - Help review and improve contributions
π Recognition
Contributors will be:
- Added to our Contributors section
- Mentioned in release notes
- Invited to join our maintainer team (for significant contributions)
Thank you for making the MCP Context Server better for everyone! π
π License
This project is licensed under the MIT License - see the file for details.
πββοΈ Support
For support and questions:
- Check the
- Run the demo script to verify functionality
- Check server logs for debugging
- Verify database configuration
π Project Structure
mcp-context-server/
βββ docker/ # Docker configuration
β βββ docker-compose.yml # Infrastructure setup
β βββ postgres/
β βββ init.sql # Database schema
βββ mcp-server/ # MCP server implementation
β βββ src/
β β βββ index.js # Main server file
β β βββ database.js # Database operations
β βββ package.json # Node.js dependencies
βββ scripts/ # Utility scripts
β βββ demo-extended-functionality.js
β βββ test-extended-apis.js
βββ EXTENDED-API-DOCS.md # Complete API documentation
βββ README.md # This file
βββ .gitignore # Git ignore patterns
Transform your development workflow with comprehensive project context management! π