# 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.

Source: https://elaichi.ai/connectors/thingworx/

## Facts

| | |
| --- | --- |
| Application | ThingWorx |
| Category | Device Management |
| AI tools | 297 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ThingWorx is connected

- 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.

## Connect ThingWorx in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ThingWorx.
2. Optionally set Share with, then press Connect.
3. Paste a ThingWorx API key. One person generates a token in ThingWorx and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ThingWorx tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ThingWorx MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## ThingWorx MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a ThingWorx tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ThingWorx through Elaichi

### Review every application key before renewal

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

### Check which authenticators are still in use

Security. 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.

### Find and fix the shift dashboard

Operations. 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.

### Look up a data shape before a change

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

### Clean out stale keys and dashboards

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

### Add a service to a field dashboard

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

## 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.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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.

## All 297 ThingWorx tools

Every tool below is callable through https://api.elaichi.ai/mcp once ThingWorx is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **List all ThingWorx application key service definitions** (List). List service definitions of a ApplicationKeys entity. Read-only. Required: application_key_name.
- **Get single ThingWorx application key metadatum by ID** (Get). Get JSON metadata of a ApplicationKeys entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx authenticators** (List). List entities in the Authenticators collection. Returns the infotable rows; read-only.
- **Get single ThingWorx authenticator by ID** (Get). Get a Authenticators entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx authenticator by ID** (Update). Update a Authenticators entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx authenticator by ID** (Delete). Delete a Authenticators entity. Id is the entity name. Required: id.
- **Create a ThingWorx authenticator service** (Create). Invoke any service on a Authenticators 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: authenticator_name, service_name.
- **List all ThingWorx authenticator service definitions** (List). List service definitions of a Authenticators entity. Read-only. Required: authenticator_name.
- **Get single ThingWorx authenticator metadatum by ID** (Get). Get JSON metadata of a Authenticators entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx dashboards** (List). List entities in the Dashboards collection. Returns the infotable rows; read-only.
- **Get single ThingWorx dashboard by ID** (Get). Get a Dashboards entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx dashboard by ID** (Update). Update a Dashboards entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx dashboard by ID** (Delete). Delete a Dashboards entity. Id is the entity name. Required: id.
- **Create a ThingWorx dashboard service** (Create). Invoke any service on a Dashboards 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: dashboard_name, service_name.
- **List all ThingWorx dashboard service definitions** (List). List service definitions of a Dashboards entity. Read-only. Required: dashboard_name.
- **Get single ThingWorx dashboard metadatum by ID** (Get). Get JSON metadata of a Dashboards entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx data shapes** (List). List entities in the DataShapes collection. Returns the infotable rows; read-only.
- **Get single ThingWorx data shape by ID** (Get). Get a DataShapes entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx data shape by ID** (Update). Update a DataShapes entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx data shape by ID** (Delete). Delete a DataShapes entity. Id is the entity name. Required: id.
- **Create a ThingWorx data shape service** (Create). Invoke any service on a DataShapes 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: data_shape_name, service_name.
- **List all ThingWorx data shape service definitions** (List). List service definitions of a DataShapes entity. Read-only. Required: data_shape_name.
- **Get single ThingWorx data shape metadatum by ID** (Get). Get JSON metadata of a DataShapes entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx data tags** (List). List entities in the DataTags collection. Returns the infotable rows; read-only.
- **Get single ThingWorx data tag by ID** (Get). Get a DataTags entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx data tag by ID** (Update). Update a DataTags entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx data tag by ID** (Delete). Delete a DataTags entity. Id is the entity name. Required: id.
- **Create a ThingWorx data tag service** (Create). Invoke any service on a DataTags 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: data_tag_name, service_name.
- **List all ThingWorx data tag service definitions** (List). List service definitions of a DataTags entity. Read-only. Required: data_tag_name.
- **Get single ThingWorx data tag metadatum by ID** (Get). Get JSON metadata of a DataTags entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx directory services** (List). List entities in the DirectoryServices collection. Returns the infotable rows; read-only.
- **Get single ThingWorx directory service by ID** (Get). Get a DirectoryServices entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx directory service by ID** (Update). Update a DirectoryServices entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx directory service by ID** (Delete). Delete a DirectoryServices entity. Id is the entity name. Required: id.
- **Create a ThingWorx directory service service** (Create). Invoke any service on a DirectoryServices 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: directory_service_name, service_name.
- **List all ThingWorx directory service service definitions** (List). List service definitions of a DirectoryServices entity. Read-only. Required: directory_service_name.
- **Get single ThingWorx directory service metadatum by ID** (Get). Get JSON metadata of a DirectoryServices entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx localization tables** (List). List entities in the LocalizationTables collection. Returns the infotable rows; read-only.
- **Get single ThingWorx localization table by ID** (Get). Get a LocalizationTables entity definition by name. Id is the entity name; read-only. Required: id.
- **Update a ThingWorx localization table by ID** (Update). Update a LocalizationTables entity (entity JSON body). Id is the entity name. Required: id.
- **Delete a ThingWorx localization table by ID** (Delete). Delete a LocalizationTables entity. Id is the entity name. Required: id.
- **Create a ThingWorx localization table service** (Create). Invoke any service on a LocalizationTables 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: localization_table_name, service_name.
- **List all ThingWorx localization table service definitions** (List). List service definitions of a LocalizationTables entity. Read-only. Required: localization_table_name.
- **Get single ThingWorx localization table metadatum by ID** (Get). Get JSON metadata of a LocalizationTables entity. Id is the entity name; read-only. Required: id.
- **List all ThingWorx logs** (List). List entities in the Logs collection. Returns the infotable rows; read-only.
- ...and 247 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
