predictive-maintenance-mcp 0.7.0

Proof of Concept: AI-Powered Predictive Maintenance & Fault Diagnosis MCP Server - Industrial machinery condition monitoring, vibration analysis, bearing diagnostics, and ML-based anomaly detection through Model Context Protocol

🏭 Predictive Maintenance MCP Server

Transform raw vibration data into actionable maintenance insights through natural conversation with AI.

A Model Context Protocol server that brings industrial machinery diagnostics directly to LLMs like Claude, enabling AI-powered vibration analysis, bearing fault detection, and predictive maintenance workflows — all through natural language.

---

🎯 Our Mission

Predictive maintenance is critical for Industry 4.0, yet expert-level machinery diagnostics remains inaccessible to most engineers. Complex diagnostic workflows — FFT spectrum analysis, envelope demodulation, ISO severity assessment — require years of specialized training.

We believe that AI can democratize this expertise.

By combining the reasoning capabilities of Large Language Models with specialized diagnostic tools through the Model Context Protocol (MCP), we create a bridge: engineers can describe a problem in plain language and receive professional-grade analysis. No signal processing PhD required.

This project is an open-source framework that proves this vision works. It's a foundation — a set of building blocks — that the community can extend, customize, and deploy for any industrial diagnostics scenario.

📖 Read the full story: Building an AI-Powered Predictive Maintenance System with MCP and Claude

---

🏗️ Ecosystem Architecture

This project is built around the Model Context Protocol (MCP) — an open standard that lets you package any software tool and make it instantly queryable by an LLM. Think of it as a USB port for AI: plug in a tool, and the LLM immediately knows how to use it.

┌──────────────────────────────────────────────────────────────┐
│   YOU (Natural Language)                                     │
│   "Is this bearing failing? Show me the envelope analysis."  │
└──────────────┬───────────────────────────────────────────────┘
               │
               ▼
┌──────────────────────────────────────────────────────────────┐
│   LLM (Claude, GPT, local models...)                         │
│   Understands your question, selects the right tools         │
└──────────────┬───────────────────────────────────────────────┘
               │  Model Context Protocol (MCP)
               ▼
┌──────────────────────────────────────────────────────────────┐
│   PREDICTIVE MAINTENANCE MCP SERVER                          │
│   ┌────────────────┐  ┌───────────────┐  ┌───────────────┐  │
│   │ FFT Analysis   │  │ Envelope      │  │ ISO 20816-3   │  │
│   │ & Reporting    │  │ Demodulation  │  │ Compliance    │  │
│   └────────────────┘  └───────────────┘  └───────────────┘  │
│   ┌────────────────┐  ┌───────────────┐  ┌───────────────┐  │
│   │ ML Anomaly     │  │ Manual/PDF    │  │ Bearing       │  │
│   │ Detection      │  │ Reader        │  │ Catalog       │  │
│   └────────────────┘  └───────────────┘  └───────────────┘  │
│   ┌────────────────┐  ┌───────────────┐                     │
│   │ RAG Document   │  │ DOCX Report   │                     │
│   │ Search (FAISS) │  │ Generation    │                     │
│   └────────────────┘  └───────────────┘                     │
└──────────────┬───────────────────────────────────────────────┘
               │
               ▼
┌──────────────────────────────────────────────────────────────┐
│   YOUR DATA (raw files stay on your machine)                 │
│   Vibration signals · Equipment manuals · Trained models     │
│                                                              │
│   ⚠️  Analysis results (peaks, RMS, diagnoses) flow back     │
│   to the LLM provider. Use a local LLM for full air-gap.     │
└──────────────────────────────────────────────────────────────┘

Key insight: The LLM doesn't know signal processing. It knows how to call tools that do signal processing. MCP is the standard that makes this plug-and-play — you can add new diagnostic tools without changing the LLM.

What This Means For You

• 🔌 Plug-and-play — Add new analysis tools (thermography, oil analysis, acoustics) as simple Python functions — the LLM discovers them automatically
• 🔒 Local processing — Raw signals never leave your machine; only computed results (peaks, RMS, diagnoses) flow to the LLM. Use a local LLM for full air-gapped privacy
• 🤖 LLM-agnostic — Works with Claude, ChatGPT, or any MCP-compatible client
• 🧱 Modular — Use only the tools you need, extend with your own

---

📑 Table of Contents

• 🎯 Our Mission
• 🏗️ Ecosystem Architecture
• 🚪 Choose Your Path
• ✨ What Makes This Special
• 🎬 Quick Examples
• 🚀 Installation
• ⚙️ Configuration
• 🔧 Available Tools & Resources
• 🤖 Copilot Skills
• 📐 Detailed Architecture
• 📊 Sample Dataset
• 💡 Usage Examples
• 📊 Professional Reports
• 📖 Documentation
• 🧪 Testing
• 🛠️ Development
• 🚀 Roadmap
• 🤝 Contributing
• 📄 License
• 📚 Citation
• 🙏 Acknowledgments

---

🚪 Choose Your Path

This project serves two audiences. Pick the door that fits you:

🔧 I'm a Maintenance / Reliability Engineer "I want to use AI for my vibration analysis and diagnostics." You don't need to write code. This tool turns your vibration data into professional reports through simple conversation. What you'll get: ISO 20816-3 compliance reports in one sentence Bearing fault detection from your real data Interactive HTML reports you can share with your team ML anomaly detection trained on your healthy baselines ➡️ Start here: Quickstart for Engineers

💻 I'm an AI / Software Developer "I want to understand MCP, extend this server, or build my own." The code is your playground. Learn how MCP works, add new diagnostic tools, or use this as a template for your own domain-specific server. What you'll learn: How MCP bridges LLMs and specialized tools How to create new tools as Python functions How to design resource/tool hybrid architectures How to contribute to an industrial open-source project ➡️ Start here: Quickstart for Developers

💡 Don't fit either profile? That's fine — read on for the full documentation, or jump to Quick Examples to see the server in action.

---

✨ What Makes This Special

• 🎯 Real Bearing Fault Data Included — 20 production-quality vibration signals from real machinery tests (3 healthy, 17 faulty)

• 📊 Professional HTML Reports — Interactive Plotly visualizations with automatic peak detection and frequency markers

• 🤖 ML Anomaly Detection — Train unsupervised/semi-supervised models (OneClassSVM/LOF) on healthy baselines with optional hyperparameter tuning

• 📏 ISO 20816-3 Compliance — Industry-standard vibration severity assessment built-in

• 🔍 Advanced Diagnostics — FFT spectrum analysis, envelope analysis for bearing faults, time-domain feature extraction

  Example analysis

  

• 📁 Multi-Format Support — Load signals from CSV, MAT (MATLAB), WAV, NPY, and Parquet files

• 🔎 RAG Document Search — Vector search (FAISS + sentence-transformers) with TF-IDF fallback over machine manuals and bearing catalogs. Auto-cached.

• 📝 DOCX Reports — Generate structured Word diagnostic reports alongside interactive HTML (requires python-docx)

• 🔍 OCR for Scanned PDFs — Automatic OCR fallback (Tesseract) for image-based equipment manuals

• ⚡ LLM-Optimised Output — Tool responses return compact summaries (top peaks, statistics) instead of raw arrays, keeping LLM context windows lean

• �🚀 Zero Configuration — Works out of the box with sample data, auto-detects sampling rates from metadata

---

🎬 Quick Examples

Example 1: Bearing Fault Detection

Generate envelope report for real_train/OuterRaceFault_1.csv

Result: AI automatically:

1. Detects sampling rate from metadata (97,656 Hz)
2. Applies bandpass filter (500-5000 Hz)
3. Generates interactive HTML report with bearing fault frequencies marked
4. Identifies outer race fault at ~81 Hz with harmonics
5. Saves report to reports/envelope_OuterRaceFault_1_*.html

Example 2: ISO 20816-3 Vibration Assessment

Evaluate real_train/OuterRaceFault_1.csv against ISO 20816-3 standard

Result:

• RMS velocity: 4.5 mm/s → Zone B (Acceptable for long-term operation)
• Interactive HTML report with zone visualization
• Compliance assessment and recommendations

Example 3: Machine Manual Integration + Diagnosis

1. Extract specifications from test_pump_manual.pdf
2. Calculate bearing frequencies for SKF 6205-2RS at 1475 RPM
3. Diagnose bearing fault in signal_from_pump.csv using calculated frequencies

Result: Complete zero-knowledge diagnosis:

• Extracts: Drive end bearing SKF 6205-2RS, operating speed 1475 RPM
• Calculates: BPFO=85.20 Hz, BPFI=136.05 Hz, BSF=101.32 Hz
• Diagnoses: Outer race fault detected with 3 harmonics

📚 More examples: See Usage Examples section below or EXAMPLES.md for complete workflows

---

🚀 Installation

Option A — PyPI (recommended)

pip install predictive-maintenance-mcp

Then configure your MCP client (see Configuration below) and point it to the installed server.

Option B — From Source (development)

git clone https://github.com/LGDiMaggio/predictive-maintenance-mcp.git
cd predictive-maintenance-mcp
pip install -e .

Run the Server

# Via module (works with both pip install and editable install)
python -m predictive_maintenance_mcp

# Via console script (after pip install)
predictive-maintenance-mcp

📖 Detailed Installation Guide: See INSTALL.md for troubleshooting and advanced setup.

---

⚙️ Configuration

Claude Desktop

Add to your Claude Desktop config:

• Windows: %APPDATA%\Claude\claude_desktop_config.json
• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

If installed via pip (recommended):

{
  "mcpServers": {
    "predictive-maintenance": {
      "command": "predictive-maintenance-mcp"
    }
  }
}

If running from source (local dev):

{
  "mcpServers": {
    "predictive-maintenance": {
      "command": "C:/path/to/predictive-maintenance-mcp/.venv/Scripts/python.exe",
      "args": ["-m", "predictive_maintenance_mcp"],
      "env": {
        "PDM_PROJECT_DIR": "C:/path/to/predictive-maintenance-mcp"
      }
    }
  }
}

Important Notes:

• Replace C:/path/to/predictive-maintenance-mcp with your actual project path
• Use absolute paths — forward slashes (/) work on all platforms, including Windows
• On macOS/Linux, use .venv/bin/python instead of .venv/Scripts/python.exe
• The PDM_PROJECT_DIR env var tells the server where to find data/, models/, and reports/

After configuration, restart Claude Desktop completely.

VS Code

Add to your MCP configuration (.vscode/mcp.json or user settings):

If installed via pip (recommended):

{
  "servers": {
    "predictive-maintenance": {
      "type": "stdio",
      "command": "predictive-maintenance-mcp"
    }
  }
}

If running from source (local dev):

{
  "servers": {
    "predictive-maintenance": {
      "type": "stdio",
      "command": "/path/to/predictive-maintenance-mcp/.venv/bin/python",
      "args": ["-m", "predictive_maintenance_mcp"],
      "env": {
        "PDM_PROJECT_DIR": "/path/to/predictive-maintenance-mcp"
      }
    }
  }
}

Use .venv/Scripts/python.exe on Windows. The PDM_PROJECT_DIR env var tells the server where to find data/, models/, and reports/.

---

🔧 Available Tools & Resources

MCP Resources (Direct Data Access)

Resources provide direct read access for Claude to examine data:

📊 Vibration Signals

• signal://list — Browse all available signal files with metadata
• signal://read/{filename} — Read signal data directly (supports CSV, MAT, WAV, NPY, Parquet)

Usage: Claude can directly read signals without calling tools first.

📖 Machine Manuals

• manual://list — Browse available equipment manuals (PDF/TXT)
• manual://read/{filename} — Read manual text (first 20 pages)

Usage: Claude can answer ANY question about manual content by reading directly.

---

MCP Tools (Analysis & Processing)

Tools perform computations and generate outputs:

📊 Analysis & Diagnostics

• analyze_fft — FFT spectrum analysis with automatic peak detection
• analyze_envelope — Envelope analysis for bearing fault detection
• analyze_statistics — Time-domain statistical indicators (RMS, Crest Factor, Kurtosis, etc.)
• evaluate_iso_20816 — ISO 20816-3 vibration severity assessment
• diagnose_bearing — Guided 6-step bearing diagnostic workflow
• diagnose_gear — Evidence-based gear fault diagnostic workflow

🤖 Machine Learning

• extract_features_from_signal — Extract 17+ statistical features from vibration data
• train_anomaly_model — Train novelty detection models (OneClassSVM/LOF) on healthy data only, with optional semi-supervised hyperparameter tuning
• predict_anomalies — Detect anomalies in new signals with confidence scores

📄 Professional Report Generation

• generate_fft_report — Interactive FFT spectrum HTML report with peak table
• generate_envelope_report — Envelope analysis report with bearing fault markers
• generate_iso_report — ISO 20816-3 evaluation with zone visualization
• generate_diagnostic_report_docx — Structured Word (.docx) diagnostic report (requires python-docx)
• generate_pca_visualization_report — 2D/3D PCA projection report for anomaly exploration
• generate_feature_comparison_report — Feature-level comparison report across signals/classes
• list_html_reports — List all generated reports with metadata
• get_report_info — Get report details without loading full HTML

💡 HTML reports are interactive Plotly visualizations saved to reports/. DOCX reports are structured Word documents for stakeholders.

📖 Machine Documentation Reader

• list_machine_manuals — List available equipment manuals (PDF/TXT)
• extract_manual_specs — Extract bearings, RPM, power from manual (with caching)
• calculate_bearing_characteristic_frequencies — Calculate BPFO/BPFI/BSF/FTF from geometry
• read_manual_excerpt — Read manual text excerpt (configurable page limit)
• search_bearing_catalog — Search bearing geometry in local catalog (20+ common bearings)
• search_documentation — Semantic search across machine manuals and bearing catalogs (FAISS vector search or TF-IDF fallback)

MCP Resources:

• manual://list — Browse available manuals
• manual://read/{filename} — Read manual for LLM context

🎯 Upload pump manual → Extract bearing specs → Auto-calculate frequencies → Diagnose signal

🔍 Data Management & Visualization

• list_signals — Browse available signal files with metadata
• generate_test_signal — Create synthetic signals for testing
• plot_signal — Generate time-domain signal plot
• plot_spectrum — Generate FFT spectrum plot
• plot_envelope — Generate envelope spectrum plot

---

Copilot Skills (Guided Workflows)

The skills/ directory contains pre-built guided workflows that orchestrate multiple MCP tools into structured diagnostic procedures:

Skill	Steps	Description
bearing-diagnosis	8	Complete bearing fault detection: statistics → FFT → envelope → frequency matching → ISO severity → report
quick-screening	5	Fast health screening with clear Healthy/Suspicious/Critical classification
report-generation	6	Professional HTML report generation with composite multi-report option

⚠️ Skills are Claude / GitHub Copilot-specific. They use SKILL.md with YAML frontmatter, a convention recognised by Claude.ai, Claude Code, and Copilot agents. Other LLM clients can still read them as plain markdown, but automatic skill invocation requires a Claude or Copilot-compatible host.

MCP tools, resources, and HTML reports are LLM-agnostic — they work with any MCP-compatible client (ChatGPT, Ollama, LM Studio, etc.).

---

📐 Detailed Architecture

The system follows a hybrid MCP architecture combining Resources (direct data access) and Tools (computational processing):

Detailed Structure

┌─────────────────────────────────────────────────────────────┐
│                    CLAUDE / LLM CLIENT                      │
└────────────────────┬────────────────────────────────────────┘
                     │
                     ▼
┌─────────────────────────────────────────────────────────────┐
│                   MCP SERVER (FastMCP)                      │
│  ┌──────────────────────────────────────────────────────┐  │
│  │  RESOURCES (Direct Data Access)                      │  │
│  │  ┌────────────────────────────────────────────────┐  │  │
│  │  │  Vibration Signals                             │  │  │
│  │  │  • signal://list                               │  │  │
│  │  │  • signal://read/{filename}                    │  │  │
│  │  └────────────────────────────────────────────────┘  │  │
│  │  ┌────────────────────────────────────────────────┐  │  │
│  │  │  Machine Manuals                               │  │  │
│  │  │  • manual://list                               │  │  │
│  │  │  • manual://read/{filename}                    │  │  │
│  │  └────────────────────────────────────────────────┘  │  │
│  └──────────────────────────────────────────────────────┘  │
│  ┌──────────────────────────────────────────────────────┐  │
│  │  TOOLS (Analysis & Processing)                       │  │
│  │  • FFT, Envelope, ISO 20816-3                        │  │
│  │  • ML Anomaly Detection                              │  │
│  │  • Report Generation (HTML + DOCX)                   │  │
│  │  • Manual Spec Extraction                            │  │
│  │  • Bearing Frequency Calculation                     │  │
│  │  • Bearing Catalog Search                            │  │
│  │  • RAG Document Search (FAISS / TF-IDF)               │  │
│  └──────────────────────────────────────────────────────┘  │
└────────────────────┬────────────────────────────────────────┘
                     │
        ┌────────────┴────────────┐
        ▼                         ▼
┌──────────────────┐   ┌──────────────────────────────────┐
│  SIGNAL ANALYSIS │   │  DOCUMENT READER MODULE          │
│  MODULE          │   │  ┌────────────┐  ┌────────────┐  │
│  • FFT Engine    │   │  │ PDF Extract│  │ ISO Formulas│  │
│  • Envelope      │   │  │ (pypdf)    │  │ BPFO/BPFI   │  │
│  • Filters       │   │  └────────────┘  └────────────┘  │
│  • Statistics    │   │  ┌─────────────────────────────┐  │
│  • ML Models     │   │  │  Bearing Catalog DB         │  │
│  • Plotly Charts │   │  │  • 20+ ISO bearings         │  │
│                  │   │  └─────────────────────────────┘  │
└────────┬─────────┘   └────────┬─────────────────────────┘
         │                      │
         ▼                      ▼
┌─────────────────────────────────────────────────────────────┐
│                   LOCAL FILE SYSTEM                         │
│  ┌──────────────────────┐   ┌──────────────────────────┐   │
│  │  data/signals/       │   │  resources/              │   │
│  │  ├── real_train/     │   │  ├── machine_manuals/    │   │
│  │  ├── real_test/      │   │  ├── bearing_catalogs/   │   │
│  │  └── samples/        │   │  ├── datasheets/         │   │
│  └──────────────────────┘   │  └── cache/ (auto)       │   │
│  ┌──────────────────────┐   └──────────────────────────┘   │
│  │  reports/            │   ┌──────────────────────────┐   │
│  │  • FFT reports       │   │  models/                 │   │
│  │  • Envelope reports  │   │  • Trained ML models     │   │
│  │  • ISO reports       │   │  • Scalers, PCA          │   │
│  └──────────────────────┘   └──────────────────────────┘   │
└─────────────────────────────────────────────────────────────┘

Key Features:

• ✅ 4 MCP Resources — Direct read access to signals and manuals
• ✅ 27 MCP Tools — Complete diagnostic workflow (analysis, plotting, ML, reporting incl. DOCX, manuals, RAG search)
• ✅ 3 Copilot Skills — Guided diagnostic workflows (Claude / Copilot-specific)
• ✅ Hybrid Architecture — Resources for reading, Tools for processing
• ✅ Local-First — All data stays on your machine (privacy-preserving)

---

📊 Sample Dataset

The server includes 20 real bearing vibration signals from production machinery:

Training Set (14 signals):

• ✅ 2 Healthy Baselines — Normal operation data
• 🔴 7 Inner Race Faults — Variable load conditions
• ⚠️ 5 Outer Race Faults — Various severity levels

Test Set (6 signals):

• ✅ 1 Healthy Baseline — Validation data
• 🔴 2 Inner Race Faults — Test conditions
• ⚠️ 3 Outer Race Faults — Test conditions

Note: Sampling rates and durations vary by signal (48.8-97.7 kHz, 3-6 seconds). All parameters auto-detected from metadata files.

📖 Full dataset documentation: data/README.md

---

💡 Usage Examples

Quick Fault Detection

Diagnose bearing fault in real_train/OuterRaceFault_1.csv
BPFO=81.13 Hz, BPFI=118.88 Hz, BSF=63.91 Hz, FTF=14.84 Hz

Result: ✅ Outer race fault detected at ~81 Hz with harmonics

Generate Professional Report

Generate envelope report for real_train/OuterRaceFault_1.csv

Result: Interactive HTML saved to reports/ with bearing fault markers

Train ML Anomaly Detector

Train anomaly model on baseline_1.csv and baseline_2.csv
Validate on OuterRaceFault_1.csv

Result: Model detects fault with 95%+ confidence

📚 More examples: EXAMPLES.md for complete diagnostic workflows

---

📊 Professional Reports

All analysis tools generate interactive HTML reports with Plotly visualizations:

Why HTML Reports?

✅ Universal — Works with any LLM (Claude, ChatGPT, local models)
✅ Zero tokens — Files saved locally, not in chat
✅ Interactive — Pan, zoom, hover for details
✅ Professional — Publication-ready visualizations
✅ Persistent — Save for documentation and sharing

Report Types

Report	Tool	Contents
🔊 FFT Spectrum	generate_fft_report()	Frequency analysis, peak detection, harmonic markers
🎯 Envelope Analysis	generate_envelope_report()	Bearing fault frequencies, modulation detection
📏 ISO 20816-3	generate_iso_report()	Vibration severity zones, compliance assessment
📝 Diagnostic DOCX	generate_diagnostic_report_docx()	Word document with stats, peaks, ISO, diagnosis

All reports include:

• Interactive Plotly charts (pan/zoom/hover)
• Automatic peak detection with frequency tables
• Metadata (signal info, analysis parameters)
• Timestamp and file references

Usage:

Generate FFT report for baseline_1.csv

→ Opens reports/fft_spectrum_baseline_1_20251111_143022.html in browser

---

📖 Documentation

Document	Audience	Description
Quickstart for Engineers	🔧 Engineers	Get results fast, no coding required
Quickstart for Developers	💻 Developers	Understand MCP, extend the server
EXAMPLES.md	Everyone	Complete diagnostic workflows with step-by-step tutorials
INSTALL.md	Everyone	Detailed installation and troubleshooting guide
CONTRIBUTING.md	Contributors	How to contribute (for every skill level)
Ollama Guide	Engineers	Use with local LLMs (fully air-gapped)
CHANGELOG.md	Everyone	Version history
data/README.md	Everyone	Dataset documentation
skills/	🤖 Claude / Copilot	Copilot Skills — guided diagnostic workflows (bearing, screening, reporting)

---

🧪 Testing

This project includes a comprehensive test suite covering all analysis tools:

# Run all tests
pytest

# Run with coverage report
pytest --cov=src --cov-report=html

# Run specific test file
pytest tests/test_fft_analysis.py

# Run with verbose output
pytest -v

Test coverage includes:

• ✅ FFT analysis and peak detection
• ✅ Envelope analysis and bearing fault detection
• ✅ ISO 20816-3 evaluation and zone classification
• ✅ ML tools (feature extraction, training, prediction)
• ✅ Report generation system (HTML outputs)
• ✅ Real bearing fault data validation

See tests/README.md for detailed testing documentation.

---

🛠️ Development

Install Development Dependencies

pip install -e ".[dev]"

Code Quality

# Format code
black src/

# Type checking
mypy src/

# Linting
flake8 src/

Debugging

Use MCP Inspector for interactive testing:

npx @modelcontextprotocol/inspector npx predictive-maintenance-mcp

Or from source (with venv active):

npx @modelcontextprotocol/inspector python -m predictive_maintenance_mcp

---

🚀 Roadmap

✨ Recent: v0.7.0 — Vector Search, OCR & DOCX Reports

• 🔎 FAISS vector search — Semantic document retrieval with sentence-transformers (TF-IDF fallback when not installed)
• 🔍 OCR for scanned PDFs — Automatic Tesseract OCR fallback for image-based equipment manuals
• 📝 DOCX diagnostic reports — Structured Word documents with statistics, peaks, ISO evaluation, and diagnostic summary
• ⚡ Compact FFT output — Top-20 peaks + RMS/stats instead of full arrays (~200 KB → ~2 KB)

🔮 Planned Enhancements

Each item below links to an open issue where you can discuss, contribute, or claim the task:

Priority	Enhancement	Status	Get Involved
✅ Done	Parquet/MAT/WAV/NPY data format support	v0.5.0	—
🔴 High	Customizable ISO report thresholds	Open	Good First Issue
🔴 High	Docker image for zero-install setup	Open	Help Wanted
✅ Done	Vector search for large documents (FAISS + sentence-transformers)	v0.7.0	—
✅ Done	OCR for scanned PDF manuals (Tesseract)	v0.7.0	—
✅ Done	DOCX diagnostic reports (python-docx)	v0.7.0	—
🟡 Medium	Multi-signal trending — Compare historical data	Planned	Discuss
🟢 Future	Real-time streaming — Live vibration monitoring	Concept	—
🟢 Future	Dashboard — Multi-asset fleet monitoring	Concept	—
🟢 Future	Online bearing catalog — Web search for unknown bearings	Concept	—
🟢 Future	Multimodal fusion — Vibration + temperature + acoustic	Concept	—

💡 Have ideas? Open a discussion or create an issue!

---

🤝 Contributing

We welcome contributions from everyone — not just programmers. See our full CONTRIBUTING.md guide, which includes specific paths for:

• 🔧 Domain experts — Validate signals, add datasets, review diagnostic logic
• 💻 Developers — Add tools, fix bugs, improve architecture
• 📖 Technical writers — Improve docs, add tutorials, translate content
• 🧪 Testers — Edge cases, validation with ground truth data

Quick Start for Contributors

1. Browse Issues — look for good first issue or help wanted labels
2. Comment on the issue to claim it
3. Fork → Branch → Code → Test → PR

See CONTRIBUTING.md for detailed setup and guidelines.

---

📄 License

This project is licensed under the MIT License — see the LICENSE file for details.

Note: Sample data is licensed CC BY-NC-SA 4.0 (non-commercial). For commercial use, replace with your own machinery data.

---

📚 Citation

If you use this server in your research or projects, please cite:

@software{dimaggio_predictive_maintenance_mcp_2025,
  title = {Predictive Maintenance MCP Server: An open-source framework for integrating Large Language Models with predictive maintenance and fault diagnosis workflows},
  author = {Di Maggio, Luigi Gianpio},
  year = {2025},
  version = {0.7.0},
  url = {https://github.com/LGDiMaggio/predictive-maintenance-mcp},
  doi = {10.5281/zenodo.17611542}
}

---

🙏 Acknowledgments

• FastMCP framework by @jlowin
• Model Context Protocol by Anthropic
• Sample Data from MathWorks
• Development Assistance: Core codebase and demonstration examples were developed with assistance from Claude by Anthropic to rapidly prototype and demonstrate the Model Context Protocol (MCP) concept for predictive maintenance applications.

⚠️ Development Notice: This codebase was generated using Claude AI under human supervision to explore and validate MCP-based approaches for industrial diagnostics and predictive maintenance workflows. While the implementation demonstrates the potential of AI-assisted development for specialized engineering domains, thorough testing and validation are required before any production or safety-critical use.

---

📬 Support

• Issues: https://github.com/LGDiMaggio/predictive-maintenance-mcp/issues
• Discussions: https://github.com/LGDiMaggio/predictive-maintenance-mcp/discussions
• Blog post: Building an AI-Powered Predictive Maintenance System with MCP and Claude

---

Built with ❤️ for condition monitoring professionals and the open-source community