ChirpStack vs DELMIA Apriso

In-depth architectural comparison of the ChirpStack and DELMIA Apriso MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose ChirpStack when:

• You need dedicated capabilities in the Industrial & IoT domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore ChirpStack Details

Choose DELMIA Apriso when:

• You need dedicated capabilities in the Industrial & IoT domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: iqms_workorders_list, iqms_workorders_get, iqms_inventory_onhand.

Explore DELMIA Apriso Details

Feature & Specification Comparison

Specification	ChirpStack Industrial & IoT	DELMIA Apriso IQMS Industrial & IoT
Summary	Manage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API	MCP server for IQMS (DELMIAworks) ERP — manufacturing, inventory, production, and quality.
Category & Scope	Industrial & IoT	Industrial & IoT

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "chirpstack": {
      "command": "uvx",
      "args": [
        "chirpstack-mcp-server"
      ]
    }
  }
}

{
  "mcpServers": {
    "iqms-delmia-apriso-2": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/iqms-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons