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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nodeblue-AI/bridge-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server