MCP PLC Core
Universal 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.
README
MCP PLC Core š
Universal MCP Server for industrial PLC communication ā works with ANY PLC.
Connect any industrial controller to AI agents (Claude, GPT, OpenClaw) via MCP protocol. Siemens, Schneider, ABB, Mitsubishi, Omron, Allen-Bradley, WAGO, CODESYS, Arduino, ESP32, or any custom PLC ā write an adapter and it just works.
Don't see your PLC? Write an adapter ā takes 15 minutes. Just implement 6 methods in the
PLCAdapterinterface.
AI Agent (Claude, GPT, OpenClaw)
ā MCP protocol (stdio)
MCP PLC Core
ā your adapter (Modbus, S7, OPC UA, EtherNet/IP...)
PLC ā Sensors, Alarms, Motors, Actuators
Quick Start
# Install
npm install mcp-plc-core
# Schneider / ABB / WAGO / CODESYS / Arduino
PLC_HOST=192.168.1.100 npx mcp-plc --adapter modbus
# Siemens S7-1200/1500/300/400
npm install nodes7
PLC_HOST=192.168.1.100 npx mcp-plc --adapter s7
# Mitsubishi / Omron / Allen-Bradley / anything else
npx mcp-plc --adapter ./my-custom-adapter.js
Built-in Adapters
| Adapter | Protocol | Port | PLC Types |
|---|---|---|---|
modbus |
Modbus TCP | 502 | Schneider, ABB, WAGO, CODESYS, Arduino |
s7 |
S7 (RFC1006) | 102 | Siemens S7-1200/1500/300/400 |
Custom Adapter ā Works with ANY PLC
Implement the PLCAdapter interface for your PLC. Regardless of manufacturer, protocol, or model ā if it has TCP/IP or serial connectivity, you can write an adapter.
PLCs you can write adapters for:
- Siemens S7-200/300/400/1200/1500/1700
- Schneider M340/M580/Modicon
- ABB AC500/AC580
- Mitsubishi MELSEC iQ-R/F/L
- Omron NJ/NX/NP
- Allen-Bradley ControlLogix/CompactLogix
- WAGO PFC200/750
- CODESYS-based controllers
- Bosch Rexroth IndraMotion
- Beckhoff TwinCAT
- Fanuc CNC (FOCAS)
- Haas / DMG Mori / Mazak
- Arduino + EthernetShield
- ESP32 + Modbus/S7 gateway
- Any custom TCP/UDP protocol
import { PLCAdapter, SensorData, AlarmData, StatusData, SetpointData, OutputData } from "mcp-plc-core";
export class MyPLCAdapter implements PLCAdapter {
readonly name = "My PLC";
readonly protocol = "my-protocol";
async connect() { /* ... */ }
async disconnect() { /* ... */ }
isConnected(): boolean { /* ... */ }
async readSensors(): Promise<SensorData> {
return {
temperature: 25.3,
pressure: 6.2,
motorSpeed: 1500,
production: 1234,
};
}
async readAlarms(): Promise<AlarmData> {
return { active: [], count: 0 };
}
async readStatus(): Promise<StatusData> {
return { status: "running" };
}
async readSetpoints(): Promise<SetpointData> {
return { temperature: 25, pressure: 6, speed: 1500 };
}
async readOutputs(): Promise<OutputData> {
return { green: true, yellow: false, red: false };
}
async writeSetpoint(parameter: string, value: number): Promise<boolean> {
// Write to your PLC...
return true;
}
}
Then use it:
import { startServer, MyPLCAdapter } from "mcp-plc-core";
const adapter = new MyPLCAdapter();
await startServer({
adapter,
limits: {
temperature: { min: 0, max: 50 },
pressure: { min: 0, max: 10 },
},
});
MCP AI Integration
Claude Desktop / OpenClaw
{
"mcpServers": {
"plc": {
"command": "npx",
"args": ["mcp-plc", "--adapter", "modbus"],
"env": {
"PLC_HOST": "192.168.1.100",
"PLC_PORT": "502"
}
}
}
}
Siemens S7
{
"mcpServers": {
"plc": {
"command": "npx",
"args": ["mcp-plc", "--adapter", "s7"],
"env": {
"PLC_HOST": "192.168.1.100",
"PLC_SLOT": "1"
}
}
}
}
Tools
| Tool | Description | Example |
|---|---|---|
read_sensor |
Read sensor value | "What's the temperature?" |
get_alarms |
Get active alarms | "Any alarms active?" |
get_status |
Full system status | "How's the line running?" |
get_setpoints |
Current setpoints | "What are the setpoints?" |
write_setpoint |
Write setpoint (safe!) | "Set temperature to 35°C" |
get_all |
Everything at once | "Give me all data" |
Resources
| Resource | Description |
|---|---|
plc://tags |
Available sensors/tags |
plc://alarms |
Alarm definitions |
plc://status |
Current status |
plc://info |
PLC and adapter info |
Safety
- ā Read-only by default ā no writes without explicit tool call
- ā Safety limits ā configurable min/max for setpoints
- ā Audit logging ā all tool calls logged
- ā Adapter isolation ā protocol-specific errors don't leak
- ā ļø Write protection ā only setpoint registers, never I/O directly
Architecture
src/
āāā adapter.ts ā PLCAdapter interface (implement this)
āāā server.ts ā MCP server (generic, adapter-agnostic)
āāā cli.ts ā CLI entry point
āāā index.ts ā Package exports
āāā adapters/
āāā modbus.ts ā Modbus TCP adapter (built-in)
āāā s7.ts ā Siemens S7 adapter (built-in)
Writing a New Adapter
6 methods. 15 minutes. Works with any PLC.
- Create
src/adapters/myplc.ts - Implement
PLCAdapterinterface (6 methods) - Register in
cli.ts:
if (adapterName === "myplc") {
const { MyPLCAdapter } = await import("./adapters/myplc.js");
return new MyPLCAdapter({ host, port });
}
- Submit PR! š
Supported Protocols (via adapters)
| Protocol | Status | Adapter |
|---|---|---|
| Modbus TCP | ā Built-in | modbus |
| S7 (RFC1006) | ā Built-in | s7 |
| OPC UA | ā Via community | node-opcua |
| EtherNet/IP | ā Via community | ethernetip |
| BACnet | ā Via community | bacstack |
| MQTT + Sparkplug B | ā Via community | mqtt |
| Mitsubishi MC Protocol | šØ Community needed | ā |
| Omron FINS | šØ Community needed | ā |
| Allen-Bradley CIP | šØ Community needed | ā |
| Bosch Rexroth | šØ Community needed | ā |
| Fanuc FOCAS | šØ Community needed | ā |
| Haas NGC | šØ Community needed | ā |
| Any custom TCP/UDP | ā Adapter interface | PLCAdapter |
Don't see your protocol? Implement PLCAdapter ā 6 methods, 15 minutes of work. Submit a PR and it'll be in the next release.
Environment Variables
| Variable | Default | Description |
|---|---|---|
PLC_HOST |
127.0.0.1 |
PLC IP address |
PLC_PORT |
varies | PLC port (502 for Modbus, 102 for S7) |
PLC_ADAPTER |
modbus |
Adapter to use |
PLC_RACK |
0 |
Rack number (S7 only) |
PLC_SLOT |
1 |
Slot number (S7: 1, S7-300/400: 2) |
License
MIT ā use it, fork it, build adapters for your PLC.
HD WebDesign ā MCP for industrial automation
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.