Skip to content

ThingWorx MCP connector

The ThingWorx connector brings application keys, authenticators, dashboards and data shapes into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can look them up, update them and create services while signed in as themselves.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

List every application key that still needs a new expiry date.

Working in ThingWorx with Elaichi

  • List all ThingWorx application keys
  • Get single ThingWorx application key by ID
  • List all ThingWorx application key service definitions
Ask anything…
Governance / Audit log Last 24 hours
ThingWorx List all ThingWorx application key service definitions Emily Carter · ChatGPT · 9:41 AM Done
ThingWorx Get single ThingWorx application key by ID Emily Carter · ChatGPT · 9:41 AM Done
ThingWorx List all ThingWorx application keys Emily Carter · ChatGPT · 9:41 AM Done
ThingWorx Update a ThingWorx application key by ID Megan Brooks · Claude · 9:38 AM Done
ThingWorx Create a ThingWorx application key service Ryan Hayes · Cursor · 9:35 AM Done

How to connect ThingWorx to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

ThingWorx MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

ThingWorx MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

ThingWorx MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

ThingWorx MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

ThingWorx MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect ThingWorx to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with ThingWorx through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in ThingWorx is logged.

  • IT

    Review every application key before renewal

    Pull the full list of ThingWorx application keys, open the ones about to expire, and update or remove them without clicking through each entry.

  • Security

    Check which authenticators are still in use

    List the authenticators on the platform, open one to see how it is set up, and retire the ones nobody should be signing in through.

  • Operations

    Find and fix the shift dashboard

    Ask for the dashboard the plant floor opens each morning, read its details, and change its title or settings while the shift is still running.

  • Engineering

    Look up a data shape before a change

    Open a data shape by name, see its fields, and update it so the next batch of readings lands in the right columns.

  • Platform

    Clean out stale keys and dashboards

    Walk through old application keys and unused dashboards and delete the ones that have not been touched since the last project ended.

  • Service

    Add a service to a field dashboard

    Create a new dashboard service for the field team and check the existing service definitions so it matches what is already there.

Try asking

  • “List every application key that still needs a new expiry date.”
  • “Which dashboards reference the pump telemetry data shape?”
  • “Update the plant floor dashboard title to Line 3 overview.”

See all 297 ThingWorx tools →

What connecting ThingWorx gets you

6 screens from Elaichi, each doing one job for your ThingWorx account.

Elaichi Agent

Ask Elaichi to work across your apps.

List every application key that still needs a new expiry date.

Which dashboards reference the pump telemetry data shape?

Update the plant floor dashboard title to Line 3 overview.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about application keys in plain language.

Three starter prompts pull live answers from ThingWorx dashboards, keys and data shapes.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint reaches ThingWorx from any client.

Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all ThingWorx application keys List List entities in the ApplicationKeys collection. Returns the infotable rows; read-only.
Get single ThingWorx application key by ID Get Get a ApplicationKeys entity definition by name. Id is the entity name; read-only. Required: id.
Update a ThingWorx application key by ID Update Update a ApplicationKeys entity (entity JSON body). Id is the entity name. Required: id.
Delete a ThingWorx application key by ID Delete Delete a ApplicationKeys entity. Id is the entity name. Required: id.
Create a ThingWorx application key service Create Invoke any service on a ApplicationKeys entity; inputs as JSON body. Send the service inputs as top-level body fields (via the proxy for inputs not listed); the response is usually an infotable. Required: application_key_name, service_name.

Tool catalog

297 ThingWorx tools, no code to write.

Application keys, authenticators, dashboards and data shapes, every method listed and ready.

ElaichiToolboxes
Name Source template Tools Created

IT toolbox

ThingWorx · application keys and renewals

ThingWorx starter 18 Mar 4, 2026

Security toolbox

ThingWorx · authenticators and sign-in

— 9 Mar 2, 2026

Operations toolbox

ThingWorx · plant floor dashboards

— 24 Feb 27, 2026

Engineering toolbox

ThingWorx · data shapes and fields

ThingWorx starter 6 Feb 19, 2026

Platform toolbox

ThingWorx · services and definitions

— 31 Jan 30, 2026

Service toolbox

ThingWorx · field team dashboards

— 12 Jan 22, 2026

Toolboxes

Each team gets its own ThingWorx toolbox.

Scope dashboards to operations and application keys to IT, one toolbox per team.

ElaichiConnections
Connection Scope Status Access
TH

ThingWorx (Platform IT)

Connected by Emily Carter

Personal • Active 1 team · 6 members
TH

ThingWorx (Security)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
TH

ThingWorx (Plant operations)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
TH

ThingWorx (Engineering)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
TH

ThingWorx (Field service)

Connected by Ryan Hayes

Personal • Active Not shared
TH

ThingWorx (Sandbox)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work in ThingWorx without the key.

One person connects the account, shares it with teams, and nobody else sees a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

ThingWorx Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

ThingWorx Application keys Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

ThingWorx Application keys List Toolbox

Audit log

Every ThingWorx change names who made it.

When, who, what happened, type and resource, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

ThingWorx digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch application keys

    ThingWorx

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    ThingWorx

    Queued

Workflows

A schedule fetches dashboards and posts a digest.

ThingWorx dashboards are grouped, drafted into a summary, approved by a person, then posted back.

ThingWorx health

Refreshed 4 minutes ago · every 15 minutes · from the application keys collection

Live

Application keys

1,284 ↓ 12%

Authenticators

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Application keys created

Last 14 days

By team

Share of activity

Platform IT 34%

Security 27%

Plant operations 21%

Engineering 18%

Collections and dashboards

ThingWorx health numbers, refreshed without asking.

Four metrics, fourteen days of application keys created, and a breakdown by team, no model involved.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for ThingWorx

All three can connect ThingWorx to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for ThingWorx, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over ThingWorx tools Allow or restrict single ThingWorx tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per ThingWorx call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

ThingWorx tools for your AI agents

297 tools are ready to call through Elaichi's MCP endpoint the moment you connect ThingWorx, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect ThingWorx to Claude?

Connect ThingWorx in Elaichi by pasting the API key from your ThingWorx platform, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once it is done, you sign in to Elaichi from Claude as yourself and ThingWorx is ready to ask about.

Does ThingWorx work with ChatGPT and Cursor as well as Claude?

Yes. ThingWorx is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, the Elaichi Agent and any other MCP client. You never set ThingWorx up a second time for a different client.

What can an AI agent actually do with my ThingWorx data?

With ThingWorx connected, an agent can list your application keys, authenticators, dashboards and data shapes, open any one of them, update it, delete it, and create new services and read their definitions. In practice that means asking for every key that expires this month, or the fields on a data shape, and getting an answer from the live platform. Short, concrete asks work better than long sentences.

Does connecting ThingWorx give the AI everything on the platform?

No. Every call into ThingWorx runs inside the access of the person who signed in to Elaichi, so an agent can only reach the keys, authenticators, dashboards and data shapes that person could already open. Elaichi can narrow that access with roles and restrictions, and it can never widen it beyond what ThingWorx itself allows.

Can my team share one ThingWorx connection?

Yes. One person connects ThingWorx in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records their name on every ThingWorx action, not the name of whoever connected it.

Can I stop an agent from deleting or changing things in ThingWorx?

Yes. In Elaichi you restrict ThingWorx actions one at a time, such as deleting an application key or updating a dashboard, and the restriction applies to a role or to one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to a ThingWorx connection when someone leaves?

Offboarding that person in Elaichi ends their access to ThingWorx through every client at once. A ThingWorx connection that was shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting ThingWorx once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

Does the ThingWorx MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. ThingWorx is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for ThingWorx?

Yes. Both let Claude, ChatGPT or Cursor use ThingWorx. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ThingWorx call.

How is Elaichi different from Composio for ThingWorx?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ThingWorx: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put ThingWorx in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot