bridge-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health check — verify the server is running. |
| correlate_projectsA | 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). |
| trace_tagA | 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. |
| find_unmapped_tagsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
ping and trace_tag are clearly distinct, but find_unmapped_tags returns exactly the unmatched-tag subset already produced by correlate_projects, making them overlapping in purpose. The descriptions do help an agent choose the right call, but the redundancy creates mild misselection risk.
Three tools follow a clear snake_case verb_noun pattern (correlate_projects, trace_tag, find_unmapped_tags). ping is a conventional health-check outlier but breaks the pattern slightly.
Four tools is reasonable for a narrow Ignition-to-L5X bridge, covering health, full correlation, single-tag tracing, and gap analysis. It is slightly lean and one tool (find_unmapped_tags) is arguably redundant rather than a distinct capability.
The core workflows — full correlation, per-tag end-to-end tracing, and gap analysis — are covered, with a mapping-file override supported. Gaps remain: no reverse (L5X-first) trace, no tool to generate/update the mapping file, and no export/report of results, though these are workaroundable.