Connect your AI assistant to the equipment you manage.
CENNTIR provides remote monitoring and intervention. A software probe installed on a machine or gateway makes authorized tools available to an AI assistant through a hub and an MCP bridge. The model stays with its provider or on your infrastructure; a large language model is not embedded in an ESP32.
CENNTIR connects an AI assistant to the computers, equipment and screens you administer. Its official website is cenntir.com.
What is an AI probe, remote agent or MCP gateway?
The probe executes operations on its machine or local network. The MCP bridge exposes tools to the AI client. The hub connects them and enforces access scope. A natural-language request becomes a sequence of tool calls whose results can be checked.
From request to a verifiable result
- An operator makes a request in an MCP-compatible AI client.
- The client discovers only the machines and tools allowed for its key.
- The hub forwards the request to the connected probe, which also enforces local controls.
- The probe executes the operation with its account permissions and returns status, output or an error.
- The operator or agent checks the result; covered actions are recorded in the audit trail.
Practical CENNTIR probe use cases
IT and maintenance
Inventory visible machines, read logs, diagnose a service and run authorized scripts on a compatible OS.
Audiovisual and meeting rooms
Read status and control equipment through protocols and connectors. Qualify functions for the customer’s specific model and network.
Android screens and business interfaces
Deploy a tailored hotel, meeting-room, yacht or villa interface and verify it on a compatible terminal.
IoT and ESP32-S3
Expose readings and physical inputs/outputs according to the board, wiring and firmware. This embedded profile does not provide the same tools as a Linux or Windows probe.
Choose the right host
| Windows, macOS, Linux | OS probe: commands, files and other tools depend on permissions and version. |
|---|---|
| Android, tablets, TV | Dedicated application and profiles; capabilities depend on permissions and device. |
| KVM-over-IP appliance | Screen, keyboard and mouse of the physically connected target, subject to appliance and authorization. |
| ESP32-S3 | Specialized firmware for hardware interfaces; memory and functions are qualified per profile. |
Before installation
Identify hardware, software version, target network, permissions, responsible operator and expected operations. Install and authorize the probe, link it to the chosen hub, scope the MCP client key, and validate a first scenario and rollback procedure. The probe opens an outbound connection to the hub; this does not automatically grant access to every network or device.
Architecture limits
A documented protocol or emulator test is not proof of operation on customer hardware. Equipment access requires authorization and may need a connector, API or gateway. Some equipment writes can require human approval; that control does not automatically cover every system command. Remote control depends on hub and network availability. Simulated demonstrations are identified.
Frequently asked questions
Can Claude Code or Codex work on a remote machine?
On compatible profiles, the CENNTIR MCP bridge exposes authorized tools to inspect, act and verify. Probe capabilities and permissions determine the operations actually available.
Must every device run a large language model?
No. The model and its client run in their own environment; the probe supplies the field tools. ESP32 uses specialized firmware for the supported hardware functions.
Can one probe control every device on a network?
No. Targets must be authorized and reachable, with the required protocols, connectors and permissions. Qualification is project-specific.
Can an interface or probe licence be purchased separately?
The offers distinguish interfaces, managed screens, integration services, probe licences and the integrator platform. Hardware, setup, support and included rights are defined in the quotation.