Skip to main content
Glama
KonnectSuite

bridge-mcp-server

by KonnectSuite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to bridge-mcp-server

No user-submitted related servers found.

    Related Servers

    • bridge-mcp-server

      Nodeblue-AI
      A
      license
      A
      quality
      A
      maintenance
      Connects Ignition SCADA and Studio 5000 PLC to correlate tags end-to-end, trace signal chains, and find commissioning gaps.
      4
      8
      MIT

    • PLCs.ai MCP Server

      PLCsai
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to connect to Allen-Bradley, Siemens, and CODESYS PLC projects for discovering, asking questions about, analyzing, and proposing code changes, with access to live tag values and version exports under permission-scoped controls.
      -

    • x402-industrial-mcp

      xXbrucyjucyXx
      A
      license
      Not graded
      quality
      D
      maintenance
      The first and only MCP server for PLC (Programmable Logic Controller) intelligence. Give any AI agent direct access to industrial automation data — ladder logic, tag databases, cross-references, fault root cause analysis, and sequence blockers
      MIT

    • OT-AIops

      industrial-aiops
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with safe, governed read access to industrial control systems (OPC-UA, Modbus, S7, Mitsubishi, MTConnect, MQTT/Sparkplug) plus cross-protocol diagnostics for troubleshooting data breaks, alarm floods, and unhealthy tags.
      155
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources