bridge-mcp-server
Rank #28014glama/Nodeblue-AI/bridge-mcp-server
Connects Ignition SCADA and Studio 5000 PLC to correlate tags end-to-end, trace signal chains, and find commissioning gaps.
bridge-mcp-server is a Model Context Protocol (MCP) server published by Nodeblue-AI. It ranks #28014 of 58,900 servers tracked on MCP Toplist, and its repository has 3 GitHub stars. bridge-mcp-server is listed on Glama, and ships as a single rolling release with no explicit version metadata. It was first listed on May 29, 2026.
Ranks ahead of 30,886 of 58,900 servers on MCP Toplist.
Use bridge-mcp-server
bridge-mcp-server doesn’t publish a machine-readable install config. Follow the setup instructions in its repository ↗, or open one of its registry listings above.
Listed on 1 registry
Nodeblue-AI
Other servers by Nodeblue-AI
View all Nodeblue-AI servers →Not versioned
This server is published through a registry that does not expose explicit version metadata, and no GitHub release tags were found on the linked repository. The listing tracks a single rolling release.
Frequently asked questions
- What is bridge-mcp-server?
- Connects Ignition SCADA and Studio 5000 PLC to correlate tags end-to-end, trace signal chains, and find commissioning gaps.
- Who maintains bridge-mcp-server?
- bridge-mcp-server is maintained by Nodeblue-AI, which publishes 1 MCP server (0 total versions) tracked on MCP Toplist.
- Is bridge-mcp-server an official MCP server?
- bridge-mcp-server is not on the Official MCP Registry. It is listed on Glama.
- How many versions does bridge-mcp-server have?
- bridge-mcp-server ships as a single rolling release with no explicit version metadata.
- Where can I find the source code for bridge-mcp-server?
- The source code for bridge-mcp-server is hosted at github.com/Nodeblue-AI/bridge-mcp-server.