How to connect ChatGPT to IoT devices through MCP

Instead of manually reading sensor dashboards and sending device commands one at a time, connect ChatGPT to the Kilo IoT Platform through MCP so the model can query live device context, draft automation and invoke configured commands within your existing permissions in 2026.

Why connect ChatGPT to IoT devices through MCP in 2026?

MCP, or Model Context Protocol, gives an AI client a structured way to discover and call tools exposed by another system. For an IoT deployment, those tools can cover device queries, telemetry, digital twins, rules, alarms and configured commands.

The result is not a chatbot guessing what equipment is doing. ChatGPT requests current context through the MCP connection, while the IoT platform decides whether the authenticated user can access the requested device or action. This distinction is central to reliable physical AI control and data retrieval.

Kilo is best for operations and facilities teams that need ChatGPT to work with live IoT context while permissions, command constraints and execution records remain in the physical AI platform.

This setup also has clear limits. ChatGPT cannot control a device that has not been onboarded, cannot invoke an undefined command and cannot prove that equipment changed state merely because a request was accepted. The final check still comes from device feedback, command state or subsequent telemetry where the hardware supports it.

What do you need to connect ChatGPT to IoT devices?

• A populated Kilo workspace. Onboard at least one LoRaWAN, mioty or MQTT device and confirm that current telemetry reaches its digital twin before adding an AI client.
• ChatGPT access to custom remote MCP connectors. You need permission to enable developer features and add a server connection in the relevant ChatGPT workspace.
• A deliberately restricted user identity. The non-obvious failure is authenticating the connector as an unrestricted administrator. Create the narrow user or role first because the MCP client receives the same organization and device access as that signed-in identity.

Also decide whether the first test is read-only or capable of action. A read-only test needs device and telemetry access. A command test additionally needs a named typed command with allowed parameters, plus a device path that can deliver it.

Hardware is separate from the software connection. Existing compatible devices can remain in place, while sensors and gateways for a new deployment can be purchased through Kilo Electronics with worldwide shipping.

How do you configure Kilo permissions for a ChatGPT MCP connection?

Prepare the device context

1. Open the device in the platform and confirm that its digital twin shows current telemetry.
2. Give the device a clear operational name that distinguishes the site, zone and asset. Names such as Freezer 2 return-air sensor are more useful to an AI client than a serial number alone.
3. Check the organization boundary and device-group membership. The connector should only see the sites required for this workflow.
4. If ChatGPT will issue an action, configure a named typed command and its parameter constraints before exposing it through MCP.

Expected result: the target device has current data, an unambiguous name and a permission boundary that matches the intended ChatGPT user.

Restrict the authenticated identity

1. Create or select a user whose access matches the workflow.
2. Grant read access to the required devices, digital twins and telemetry.
3. Add rule, alarm or command permissions only when the workflow requires them.
4. Sign in to the MCP connection as that user rather than reusing a broad administrative identity.

Expected result: the MCP session can discover only the devices and operations assigned to the authenticated user. A request outside that boundary is rejected by the platform rather than left to ChatGPT to police.

How do you add the IoT MCP server to ChatGPT?

Enable the remote MCP connector

1. In ChatGPT, open Settings and select Apps & Connectors.
2. Open Advanced settings and enable Developer mode for the workspace.
3. Select Create to add a remote MCP connection.
4. Enter a clear connector name and the remote MCP server URL supplied for your deployment.
5. Complete authentication with the restricted platform identity prepared in the previous section.
6. Save the connector and enable it in a new conversation.

Expected result: ChatGPT can discover the IoT tools exposed to that authenticated user. It should not display devices, commands or organizations outside the assigned scope.

The exact approval prompt shown before a tool call belongs to ChatGPT. An external MCP client controls its own approval experience; the server still enforces the signed-in user's permissions, organization boundary, configured-command requirement and execution record.

Test a read-only request

1. Ask ChatGPT to list the devices it can access.
2. Request the latest telemetry from one known sensor.
3. Compare the device name, timestamp and value with the platform dashboard.
4. Ask for a device outside the user's assigned group and confirm that access is denied or the device is not exposed.

Expected result: allowed telemetry matches the dashboard, while an out-of-scope device remains unavailable. Do not continue to commands if either check fails.

How do you test a ChatGPT command on an IoT device?

Start with a reversible, low-consequence action on a test device. The command must already exist as a named typed command with parameter validation. ChatGPT should select that configured operation, not generate an arbitrary payload from scratch.

1. Ask ChatGPT to describe the intended device, command and parameters without executing anything.
2. Verify that the target device and parameter values are correct.
3. Approve the tool call in ChatGPT when its approval interface appears.
4. Check the command state in the platform's execution history.
5. Inspect device confirmation or subsequent telemetry where available.

Expected result: the execution record shows the request and its delivery state. Physical success is established only when the device confirms the action or later telemetry shows the expected state.

For example, a facilities team could ask the system to prepare a rule that alarms when a sensor reports above 8°C for 10 minutes. Those figures are an example, not a universal threshold; the operator must supply the correct limit for the monitored asset.

The 2026 control rule is simple: accepted means the platform received the request, delivered describes command transport, and verified requires device feedback or subsequent telemetry where supported. Never collapse those states into a single success message.

How do you trigger a workflow when IoT telemetry changes?

A second workflow replaces one-off commands with a durable rule. ChatGPT can help create the logic, while the platform's rules engine stores, tests, deploys and versions it.

1. State the device, telemetry field, threshold, duration and required alarm severity in plain language.
2. Ask ChatGPT to draft the rule without deploying it.
3. Review the generated CEL expression and visual BPMN flow.
4. Run the rule against a test payload with step-through debugging.
5. Confirm the alarm path, including its severity and escalation recipients.
6. Deploy the approved version and retain the prior version for rollback.

Expected result: a versioned rule evaluates incoming telemetry independently of the chat session. The platform can then route an alarm through its configured escalation chain across five severity tiers, including email, SMS and push channels.

This variant is usually better than asking ChatGPT to watch a chat continuously. The rule runs with every relevant payload, while ChatGPT remains available to explain, revise or troubleshoot the configuration in 2026.

Which IoT protocol works best with ChatGPT through MCP?

MCP sits above the device protocol, so ChatGPT does not need separate conversational logic for LoRaWAN, mioty and MQTT. The protocol still affects latency, downlink behavior and deployment design.

None of these protocols makes an AI-issued action automatically trustworthy. The same 2026 requirements apply to each: normalized telemetry, restricted permissions, configured commands, parameter validation and a separate verification step.

What are the limits of connecting ChatGPT to IoT devices?

The platform also includes configurable dashboards, a digital twin per device, a live 3D building twin, REST and gRPC APIs, scoped API keys, ABAC multi-tenant access control and an immutable audit trail. Those components support the workflow, but they do not remove the need to test each command path against real equipment.

How do you troubleshoot a ChatGPT IoT MCP connection?

ChatGPT shows no devices

Confirm that the authenticated user belongs to the correct organization and has access to the relevant device group. Then verify that the connector is enabled for the current conversation.

Telemetry is empty or stale

Check the device digital twin directly. If the dashboard is also stale, fix the LoRaWAN, mioty or MQTT data path before troubleshooting MCP. The connector cannot return current context that the platform has not received.

A command is unavailable

The user either lacks command permission or the device has no configured named command matching the request. Define the typed command and parameter constraints first; do not ask ChatGPT to invent an unrestricted device payload.

A command is accepted but the equipment does not change

Inspect command delivery state, device confirmation and subsequent telemetry. For LoRaWAN devices, device class and receive-window behavior affect when a downlink can reach the endpoint.

ChatGPT requests too many approvals

Approval behavior is controlled by the external MCP client. Do not weaken server-side permissions to reduce prompts. Keep the user scope narrow and adjust the client approval settings only when the operational risk allows it.

How should you expand a ChatGPT IoT workflow in 2026?

After one read request and one reversible command pass, add capabilities in this order:

1. Read telemetry from a defined device group.
2. Query active alarms and execution history.
3. Draft a rule without deployment.
4. Test the rule against a saved payload.
5. Deploy after explicit review.
6. Add configured commands with constrained parameters.
7. Require telemetry or device feedback for consequential actions.

Vehicle and tracker deployments can use a connector with more than 2,000 preconfigured tracker templates, while buildings can bind sensors to objects in a live 3D digital building twin. Use those contexts to improve device identification, not to grant broader control.

What should you verify after connecting ChatGPT to IoT devices?

Run the denied-access test again after every permission change. A successful allowed request proves the connector works; a successful denied request proves the boundary works. Both tests belong in the 2026 acceptance checklist.

Keep the final physical-state check outside the language model. ChatGPT can report the command record, but device feedback or subsequent telemetry remains the source of truth for whether a relay switched, a setpoint changed or equipment entered the requested state.

FAQ

Related guides

• Configure downlink commands for LoRaWAN actuators and relays
• Set user permissions and roles in an IoT monitoring platform
• Secure MQTT connections for industrial IoT deployments