# S7 Mcp Bridge

> S7 MCP Bridge is a MCP Server that connects AI agents to Siemens industrial PLCs (specifically S7-1500 and S7-1200 models).

- **Type:** MCP server
- **Install:** `agentstack add mcp-cadugrillo-s7-mcp-bridge`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [cadugrillo](https://agentstack.voostack.com/s/cadugrillo)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [cadugrillo](https://github.com/cadugrillo)
- **Source:** https://github.com/cadugrillo/s7-mcp-bridge

## Install

```sh
agentstack add mcp-cadugrillo-s7-mcp-bridge
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# S7 MCP Bridge

**S7 MCP Bridge** is a MCP Server that connects AI agents to Siemens industrial PLCs (specifically S7-1500 and S7-1200 models). This allows AI agents to automatically monitor and control industrial equipment by sending commands and receiving data from the machines.

---

## 🔧 Available Tools

  - User authentication (`Api-Login`, `Api-Logout`, `Api-ChangePassword`)
  - Check PLC connectivity (`Api-Ping`)
  - Retrieve user permissions (`Api-GetPermissions`)
  - Get API version (`Api-Version`)
  - List available API methods (`Api-Browse`)
  - Retrieve structure information (`Api-GetQuantityStructures`)
  - Get password security policies (`Api-GetPasswordPolicy`)
  - Browse tags and metadata (`PlcProgram-Browse`)
  - Read single variables (`PlcProgram-Read`)
  - Write Boolean, Number, or String tags (`PlcProgram-Write`)
  - Read the current CPU operating mode (`Plc-ReadOperatingMode`)
  - Request a change of operating mode (`Plc-RequestChangeOperatingMode`)
  - Read the CPU system time (`Plc-ReadSystemTime`)
  - Set the CPU system time (`Plc-SetSystemTime`)
  - Read available project languages (`Project-ReadLanguages`)
  - Browse active alarms (`Alarms-Browse`)
  - Acknowledge alarms (`Alarms-Acknowledge`)
  - Browse diagnostic buffer entries (`DiagnosticBuffer-Browse`)
  - List all configured PLCs via env variables (`List-AvailablePlcs`)
  - Create backup file of the CPU (`Plc-CreateBackup`)
  - Delete a ticket provided by the system (`Api-CloseTicket`)

---

## ⚙️ Prerequisites

- [Node.js](https://nodejs.org/) (v18.x or later recommended)
- npm (comes bundled with Node.js)
- Access to a running **SIEMENS PLC API (Webserver)**

---

## ⚙️ Configuration

This server uses environment variables for configuration.

### Example `env variables`:

```bash
export PLC_IP_ADDRESSES="192.168.2.200, 192.168.2.201, 192.168.2.202"
export PLC_NAMES="PLC1, PLC2, PLC3" //optional
export MCP_SERVER_PORT=57001 //optional
export TRANSPORT="http-stream" //optional
```

## 🚀 Getting Started (Development)

1. Git Clone this repo: https://github.com/cadugrillo/s7-mcp-bridge.git 

2. Navigate to the project folder:

```bash
cd s7-mcp-bridge
```

3. Install dependencies:

```bash
npm install
```

4. Build the project:

```bash
npm run build
```

5. Edit env variables as shown above.

6. Start the server

```bash
npm run start
```

## 🐳 Docker Container

There is a Docker Container Image avaiable at https://hub.docker.com/r/cadugrillo/s7-mcp-bridge/tags

- How to run
```bash
docker run -d -p 57001:57001 -p 57002:57002 -m 512m --memory-swap=512m \
--name s7McpBridge \
-e MCP_SERVER_PORT=57001 \
-e PLC_IP_ADDRESSES="192.168.2.200, 192.168.2.201, 192.168.2.202" \
-e PLC_NAMES="PLC1, PLC2, PLC3" \
cadugrillo/s7-mcp-bridge:latest
```

**Remember to change port according to your deployment.**
**When TRANSPORT is set to "http-stream", there is a status page at http://\:[MCP_SERVER_PORT +1]/status**

- Available Environment Variables

| | | |
| :---------------------------: | :--------: | :------------------------------------------------------- |
|  PLC_IP_ADDRESSES             | required   | IP addresses of available PLCs separated by comma eg. "192.168.1.10, 192.168.1.20" |
|  PLC_NAMES                    | optional   | Names of available PLCs separated by comma eg. "Machine1, Machine2" |
|  MCP_SERVER_PORT              | optional   | If not set, it defaults to 57001, status page at http://\:57002/status |
|  TRANSPORT                    | optional   | It can be "http-stream" or "stdio". If not set it defaults to http-stream |

### 🖥️ Connecting with Claude Desktop

1. Install Claude extension (s7-mcp-bridge-vx.x.x.mcpb) found at https://github.com/cadugrillo/s7-mcp-bridge/tree/main/claude_extension.

2. Or run as a Docker Container choosing from one of the options (stdio or http-stream):

- (stdio) Find or create the claude_desktop_config.json file (typically in the Claude app config folder) and add the following:

```json
{
    "mcpServers": {
        "S7-MCP-Bridge": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "-e",
                "PLC_IP_ADDRESSES=192.168.2.200, 192.168.2.201, 192.168.2.202",
                "-e",
                "PLC_NAMES=PLC1, PLC2, PLC3",
                "-e",
                "TRANSPORT=stdio",
                "cadugrillo/s7-mcp-bridge:latest"
            ]
        }
    }
}
```

- (http-stream) Or run the docker container (instructions above) and add the following (remember to change port according to your deployment):

```json
{
  "mcpServers": {
    "S7-MCP-Bridge": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:57001/mcp"]
    }
  }
}
```

3. Or use the following if running locally for development (stdio):

```json
{
  "mcpServers": {
    "S7-MCP-Bridge": {
      "command": "node",
      "args": ["path/to/your/index.js"], //`for Windows user proper escape (eg. C:\\path\\to\\your\\index.js)`
      "env": {
        "PLC_IP_ADDRESSES":"192.168.2.200, 192.168.2.201, 192.168.2.202",
        "PLC_NAMES":"PLC1, PLC2, PLC3",
        "TRANSPORT": "stdio"
      }
    }
  }
}
```

### 🪲 Reporting bugs and contributing

- Want to report a bug or request a feature? Please open an [issue](https://github.com/cadugrillo/s7-mcp-bridge/issues/new)

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [cadugrillo](https://github.com/cadugrillo)
- **Source:** [cadugrillo/s7-mcp-bridge](https://github.com/cadugrillo/s7-mcp-bridge)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-cadugrillo-s7-mcp-bridge
- Seller: https://agentstack.voostack.com/s/cadugrillo
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.