Skip to main content
Glama
fieldpuppet

fieldpuppet

Official

Related Servers

Alternatives to fieldpuppet

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that lets AI models read and control industrial devices via standardized protocols like Modbus, OPC UA, and MQTT, with simulation and real hardware modes.
    5
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for operating, recording, and analyzing serial-connected measurement instruments and circuits via AI agents. Includes a built-in mock device so all features can be tested without physical hardware.
    -
  • A
    license
    A
    quality
    B
    maintenance
    Agent-PLC MCP Server: auto-detect, probe, read, write and diagnose Modbus TCP / FINS / MELSEC / Siemens S7comm PLCs, with transparent proxy and fault-injection listener.
    15
    27 PyPI
    2
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that connects a local LLM to an industrial PLC via Modbus TCP, enabling process reading, alarm correlation, and safe diagnosis with restricted write access through an allowlist. Includes a simulated PLC with real physics for local testing.
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    MCP server that connects AI assistants to Siemens TIA Portal via the Openness API. AI-assisted PLC programming, project management, hardware configuration, cross-reference analysis, and deployment. 19 tools, 230 actions.
    64
    -

TDQS

A4.6/5.0

Scored across 22 tools

Disambiguation5/5

Every tool targets a distinct resource+action, and the descriptions explicitly cross-reference the near neighbors (read_points vs read_registers vs get_device, set_point vs set_signal vs write_registers, remove_device vs remove_all_devices). Removal/stop variants (remove_device, remove_all_devices, remove_point, stop_scenario, clear_fault) each have clear, non-overlapping semantics. An agent can reliably pick the right tool.

Naming Consistency5/5

All names are snake_case verb_noun (list_templates, create_device, read_points, set_signal, inject_fault, save_project, load_project). Verbs are used consistently per action (list_*, get_*, remove_*, read_*/write_*, set_*), with no camelCase or style mixing.

Tool Count4/5

22 tools is on the heavy side, but the simulator genuinely spans devices, points, signals, raw registers, faults, scenarios, traffic logs and projects. Each tool maps to a needed operation rather than redundant variants. Slightly over the ideal range but well-justified.

Completeness4/5

Coverage is broad: full device lifecycle (create/clone/list/get/remove/save/load/list_projects), point add/remove/set/signal/read, raw register read/write, fault inject/clear, scenario apply/stop, and traffic log. Minor gap: no update_point to change a point's scale/unit/definition without removing and re-adding it. Core workflows are otherwise complete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues