industry4-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@industry4-mcp What is the current temperature of machine MCH-001?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
๐ญ Industry 4.0 Machine Health MCP Server
Bridging the gap between Industrial IoT Data and Conversational AI
๐ Table of Contents
Related MCP server: operational-data-mcp
๐ Overview
The Industry 4.0 Machine Health MCP Server is a Model Context Protocol (MCP) based application built for the NitroStack Hackathon.
It empowers factory operators and managers to interact with complex industrial telemetry data using simple natural language via ChatGPT.
Instead of navigating through complex dashboards, a user can simply ask:
"What is the current temperature of Machine 1?"
And ChatGPT will fetch the real-time data through this MCP server.
โ ๏ธ Problem Statement
In Industry 4.0 environments, factory machines generate telemetry data such as temperature, vibration, and RPM. In production, this would typically live in a time-series database like InfluxDB.
Today, this demo runs against an in-memory PlantDatabase in industry.data.ts, which means:
Data access is already standardized through MCP Tools
Non-technical users can query it through ChatGPT
The same tool contract can later target a real time-series database without changing the AI workflow
๐ก Solution & AI Integration
We created an MCP Server using the NitroStack SDK. This server exposes structured tools that ChatGPT can call directly, while all machine data is served from the in-memory PlantDatabase defined in src/modules/industry/industry.data.ts.
This keeps the AI layer decoupled from storage:
MCP Tools define the contract
PlantDatabaseacts as the current data sourceA future InfluxDB connector can replace it without changing the AI workflow
๐ Architecture & Flow
flowchart LR
A["Factory Machines / IoT Sensors"] -->|Telemetry Data| B["PlantDatabase industry.data.ts"]
B -->|In-Memory Mock Data| C["NitroStack MCP Server TypeScript"]
C -->|"@Tool Functions"| D["NitroCloud Hosted Deployment"]
D -->|Exposes Server URL| E["ChatGPT MCP Client"]
E -->|Natural Language Query| F["End User"]
style A fill:#ff9f43,color:#fff
style B fill:#54a0ff,color:#fff
style C fill:#5f27cd,color:#fff
style D fill:#00d2d3,color:#fff
style E fill:#10ac84,color:#fff
style F fill:#feca57,color:#333Data Flow
sequenceDiagram
participant U as "User"
participant C as "ChatGPT"
participant S as "MCP Server"
participant DB as "PlantDatabase"
U->>C: "What is the health of MCH-001?"
C->>S: Calls get_machine_health tool
S->>S: Validates input with Zod
S->>DB: Reads from industry.data.ts
DB-->>S: Returns machine data
S-->>C: JSON response
C-->>U: "Machine MCH-001 is running at 72C..."๐ Project Structure
industry4-mcp/
โโโ src/
โ โโโ index.ts # Application bootstrap
โ โโโ app.module.ts # Root application module
โ โโโ modules/
โ โโโ industry/ # Industry 4.0 module
โ โโโ industry.module.ts
โ โโโ industry.tools.ts # MCP Tools (get_machine_health)
โ โโโ industry.prompts.ts # Plant orchestrator prompt
โ โโโ industry.data.ts # In-memory PlantDatabase
โโโ widgets/ # NitroStudio UI Widgets (Next.js)
โโโ package.json # Dependencies (@nitrostack/core, zod)
โโโ .env # Environment variables๐ ๏ธ Available MCP Tools
The server currently exposes the following tool to the AI:
get_machine_health
Property | Description |
Purpose | Fetches current health status, temperature, and vibration level of a specific machine |
Input |
|
Output | JSON object with telemetry data |
Input Schema (Zod)
{
machine_id: z.string() // e.g., "MCH-001"
}Response Format
{
"machine_id": "MCH-001",
"temperature": 72.5,
"vibration_level": 0.45,
"health_status": "healthy",
"last_maintenance": "2026-07-15"
}๐ Getting Started (Local Setup)
Prerequisites
๐ข Node.js (v18+ required, v20.x recommended by NitroStack)
๐ฆ npm or npx
Installation
# 1. Clone the repository
git clone https://github.com/AryanPROOO/industry4-mcp.git
cd industry4-mcp
# 2. Install dependencies
npm install
# 3. Start the development server
npm run devThe server will start running locally on the default STDIO/HTTP port.
๐งช Testing via NitroStudio
NitroStudio is the official desktop IDE to test MCP servers before deploying them.
๐ฅ Download & Install โ Get NitroStudio from nitrostack.ai/studio
๐ Sign In โ Use your NitroCloud account
โ Add Server โ Click
Add Serverโ SelectNitro Projecttab๐ Browse Project โ Select the
industry4-mcpfolder๐ฅ๏ธ Open App Canvas โ Navigate to the Studio App Canvas
๐ง Test Tool โ Go to
Toolsโ Selectget_machine_healthโถ๏ธ Execute โ Input
MCH-001and click Execute Tool
โ๏ธ Deployment & ChatGPT Integration
Once the tool is working locally, it's time to make it live!
Step 1: Deploy to NitroCloud
In NitroStudio, click the Deploy button in the header
Follow the modal steps:
๐ฆ Preparing bundle
โฌ๏ธ Uploading
๐จ Building
โ Live
Copy your Service URL
Step 2: Connect to ChatGPT
Open ChatGPT (Plus/Pro account required)
Go to Settings โ Plugins (Apps) and enable Developer Mode
Click the + (Add Plugin) button
Select Server URL as the connection type
Paste your Service URL and add
/sseat the end:https://xyz.nitrocloud.app/sseClick Create and then Connect
Step 3: Talk to your Factory! ๐ฃ๏ธ
Try asking ChatGPT:
๐ฌ "What is the health of machine MCH-001?"
๐ฌ "Is machine 4 running hot?"
๐ฌ "Which machines need maintenance?"
๐ฎ Future Scope
Feature | Description |
๐๏ธ Live InfluxDB Integration | Replace |
๐ฎ Predictive Maintenance | Add tools that analyze historical data to predict machine failure |
๐ Alerting System | Trigger alerts to maintenance teams if vibration exceeds threshold |
๐ค Community & Links
Resource | Link |
๐ NitroStack Documentation | |
โ๏ธ NitroCloud | |
๐ฌ NitroStack Discord | |
๐ NitroStack GitHub | |
๐น YouTube | |
๐ผ LinkedIn |
Built with โค๏ธ for the NitroStack Hackathon 2026
Empowering Industry 4.0 with Conversational AI
Available Tools
6 toolsadjust_machine_parametersA
Calculates and adjusts machine tool offsets to fix quality defects (like dimension oversize) automatically. Fetches current recipe internally from the database.
Inputs: machine_id (required), defect_data (required).
generate_compliance_audit_trailA
Compiles sensor logs and operator actions into a standard PDF audit report for FDA/ISO compliance after a deviation.
Inputs: batch_id (required), deviation_event (required).
normalize_sensor_tagsA
Translates raw weird sensor names into industry standard (ISA-95) formats. Call this when new machine data arrives.
Inputs: sensors (required).
optimize_energy_scheduleC
Checks real-time energy prices and delays non-urgent jobs to off-peak hours to save electricity costs.
Inputs: job_queue (required), threshold_price (required), current_energy_price (required).
predict_maintenance_windowC
Predicts machine failure based on live sensor vibration from database.
Inputs: machine_id (required), sensor_history_hours (required).
reroute_node_red_flowA
Dynamically changes Node-RED flow configuration to reroute production data from a failed machine to a backup machine.
Inputs: product_id (required), backup_machine (required), failed_machine (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 6 tools
Each tool targets a clearly distinct domain: sensor normalization, flow rerouting, energy optimization, maintenance prediction, parameter adjustment, and compliance reporting. There is no overlap in purpose, and an agent can easily select the right tool based on the task.
All tool names follow a consistent verb_noun pattern (e.g., normalize_sensor_tags, optimize_energy_schedule, generate_compliance_audit_trail). This predictability makes the toolset easy to navigate and understand.
With 6 tools, the server is well-scoped for an Industry 4.0 domain without being overwhelming. Each tool earns its place by covering a different aspect of smart manufacturing operations.
The toolset covers a broad set of Industry 4.0 use cases: data normalization, dynamic rerouting, energy optimization, predictive maintenance, quality control, and compliance. Minor gaps exist (e.g., no explicit production monitoring or batch tracking), but agents can work around them with the provided capabilities.
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Cloud-hosted MCP server for secure AI access to enterprise data sources via CData Connect AI.
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn open-source MCP server that bridges AI models with industrial equipment, supporting multiple protocols like Modbus, OPC UA, and MQTT for reading data and controlling machines.2Apache 2.0
- AlicenseAqualityCmaintenanceMCP server that unifies real-time telemetry from industrial systems into a single queryable interface, enabling production visibility, anomaly detection, and operational insights.516 npmMIT
- AlicenseBqualityCmaintenanceUniversal MCP server for industrial PLC communication, enabling AI agents to read sensors, alarms, status, setpoints, and write setpoints via adapters for Modbus, S7, or custom PLCs.6MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.6MIT