Skip to main content
Glama

thingworx-mcp

MCP server for PTC ThingWorx, the IIoT platform. 8 tools for AI agents to read live state and trigger actions across the industrial asset graph.

What it wraps

The ThingWorx REST API surface that matters to an agent: Things, Properties, Services, ThingTemplates, and the model search index. ThingWorx is the IIoT platform used to wire SCADA, PLCs, MES, and plant equipment into a unified model. This MCP gives an agent the read path for live equipment state and the write path for setpoints and named operations, both env-gated independently because both can affect real industrial equipment.

Related MCP server: production-grade-mcp-agentic-system

Tools (8)

Tool

Purpose

Env gate

list_things

Inventory all Things in the model

none

get_thing

Read a Thing's full metadata + surface area

none

read_property

Read live value of a Property

none

write_property

Update a Property value

THINGWORX_ALLOW_WRITE=true

invoke_service

Execute a named Service on a Thing

THINGWORX_ALLOW_INVOKE=true

list_thing_templates

Inventory available ThingTemplates

none

get_thing_template

Read a ThingTemplate's definition

none

search_things

Free-text search the model

none

The two gates are independent. An operator can enable property writes (setpoints) without enabling service invocations (which can include emergency stops, PLC commands, downstream workflow triggers), and vice versa.

Install

pip install thingworx-mcp

Configuration

ThingWorx is self-hosted. Set:

export THINGWORX_BASE_URL="https://thingworx.your-company.com"
export THINGWORX_APP_KEY="your-application-key"

# Optional, default false. Enables write_property tool.
export THINGWORX_ALLOW_WRITE="true"

# Optional, default false. Enables invoke_service tool.
export THINGWORX_ALLOW_INVOKE="true"

# Optional, default true. Set to "false" for self-signed dev instances.
export THINGWORX_VERIFY_SSL="false"

Generate the appKey in ThingWorx Composer under Security > Application Keys. The MCP uses the appKey header convention (not Bearer).

Use with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "thingworx": {
      "command": "thingworx-mcp",
      "env": {
        "THINGWORX_BASE_URL": "https://thingworx.your-company.com",
        "THINGWORX_APP_KEY": "your-application-key"
      }
    }
  }
}

Use with Hermes

mcp:
  thingworx:
    command: thingworx-mcp
    env:
      THINGWORX_BASE_URL: https://thingworx.your-company.com
      THINGWORX_APP_KEY: ${THINGWORX_APP_KEY}
      THINGWORX_ALLOW_WRITE: "true"

Safety model

ThingWorx is wired to real PLCs and real equipment. The MCP defaults to read-only. Property writes and service invocations both require an explicit env opt-in, and the gates are independent so an operator who wants telemetry write capability does not have to also grant service invocation rights.

Failures from the upstream ThingWorx instance are surfaced as structured errors. Network and timeout errors are surfaced with status codes.

Development

git clone https://github.com/NoBanks/thingworx-mcp
cd thingworx-mcp
pip install -e ".[dev]"
pytest

Tests use respx for HTTP mocking, no live ThingWorx instance required.

License

MIT. See LICENSE.

About

Part of a 26 plus MCP server cohort at github.com/NoBanks, shipped by @livingagentic. Other industrial MCPs in the same cohort: workday-mcp, veeva-mcp, plaid-mcp, lambda-cloud-mcp. Built using the same factory pattern: env-gated for destructive actions, MIT licensed, install-ready, smoke-tested.

Available Tools

8 tools
get_thingA

Get metadata for a specific Thing by name. Returns the Thing's properties, services, events, and implemented ThingShapes. Used to discover the surface area of a Thing before reading or writing it.

Inputs: name (required).

get_thing_templateA

Get the full definition of a ThingTemplate by name, including property + service + event signatures, parent template, and implemented ThingShapes.

Inputs: name (required).

invoke_serviceA

Invoke a named Service on a Thing. Gated by THINGWORX_ALLOW_INVOKE=true (separate from write) because services execute named actions that can include PLC commands, scripted workflows, and downstream system calls. The MCP refuses to invoke unless the operator has explicitly authorized it.

Inputs: thing_name (required), service_name (required), parameters.

list_thingsA

List all Things registered in the ThingWorx model. Returns Thing names, descriptions, and parent ThingTemplate. The standard read path for an agent that needs to discover the industrial asset inventory.

Inputs: no named parameters.

list_thing_templatesA

List all ThingTemplates available in the ThingWorx model. ThingTemplates are the type definitions Things instantiate from. Used by agents to understand the schema available before creating or inspecting Things.

Inputs: no named parameters.

read_propertyA

Read the current value of a single Property on a Thing. Returns the property value plus its data type. The standard read path for an agent that needs the live state of an industrial asset.

Inputs: thing_name (required), property_name (required).

search_thingsA

Search the ThingWorx model by free-text expression matched against Thing names + descriptions. Returns up to max_items results. Used when the agent does not know the exact Thing name (e.g. 'find all conveyor things in Line 4').

Inputs: search_expression (required), max_items.

write_propertyA

Write a new value to a Property on a Thing. Gated by THINGWORX_ALLOW_WRITE=true because property writes can change the state of real industrial equipment (setpoints, modes, configuration). The MCP refuses to write unless the operator has explicitly authorized it.

Inputs: value (required), thing_name (required), property_name (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: property, service, thing, template, search. No overlap between read_property/write_property, list_things/search_things, or get_thing/get_thing_template.

    Naming Consistency5/5

    All tools follow a clear verb_noun pattern in snake_case (e.g., list_things, read_property, invoke_service). No mixed conventions or vague verbs.

    Tool Count5/5

    8 tools is well-scoped for an industrial MCP server covering asset discovery, state reading, property writing, and service invocation. Each tool has clear purpose.

    Completeness3/5

    Core read/write and discovery are covered, but missing create/delete for Things and ThingTemplates. Invoke/service is present but limited. Gaps in lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connect your AI workflows to the ThingsBoard IoT Platform through this MCP server. Enables LLMs to query device telemetry, manage IoT entities (devices, assets, customers), and analyze sensor data - all through natural language. Perfect for building AI-powered IoT monitoring, predictive maintenance,
      99
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Universal MCP server for industrial PLC communication, enabling AI agents to read sensors, alarms, status, setpoints, and write setpoints via adapters for Modbus, S7, or custom PLCs.
      6
      MIT