servers / bridge-mcp-server

bridge-mcp-server

communityunknownpythonverifiedhealthy

Cross-platform intelligence bridge — correlate Ignition SCADA tags with Studio 5000 PLC logic


01Tools · 4

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
ping
Health check — verify the server is running.
readfalseunknown
correlate_projects
Build a full correlation map between an Ignition project and an L5X PLC project. Walks all Ignition OPC tags, maps each to its L5X counterpart via OPC item path normalization, and returns matched pairs plus unmatched tags on both sides. Args: ignition_path: Path to Ignition project directory or .zip export. l5x_path: Path to Studio 5000 .l5x file. mapping_file: Optional JSON file with explicit tag mappings (overrides convention).
readfalseunknown
trace_tag
Trace a single tag end-to-end: Ignition config → OPC path → L5X tag → PLC logic. Returns the complete signal chain showing where the tag is defined in Ignition, what PLC tag it maps to, and every rung/line of PLC logic that references it. Args: ignition_path: Path to Ignition project directory or .zip export. l5x_path: Path to Studio 5000 .l5x file. tag_name: Ignition tag name to trace (e.g. "Running", "Conveyors/Line1/Speed"). mapping_file: Optional JSON file with explicit tag mappings.
readfalseunknown
find_unmapped_tags
Find tags that exist on one side but not the other — commissioning gap analysis. Returns Ignition OPC tags with no L5X match and L5X tags with no Ignition reference. Args: ignition_path: Path to Ignition project directory or .zip export. l5x_path: Path to Studio 5000 .l5x file. mapping_file: Optional JSON file with explicit tag mappings.
readfalseunknown

02Install & source
uvx bridge-mcp-server
uvx
pip install bridge-mcp-server
pip

05Provenance & freshness
sourcesPyPI [p4]
last_checked2026-08-16 18:54Z
next_check2026-08-17 01:03Z
cadenceevery 6h
verifiedtools_list:passed handshake:passed metadata:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed
index_statusindex8 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. bridge-mcp-server MCP — as seen on mcpexplorer.com

[![bridge-mcp-server MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/bridge-mcp-server.svg)](https://mcpexplorer.com/servers/bridge-mcp-server)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →
bridge-mcp-server — MCPExplorer