Skip to content
DataRemote

New DataRemote MCP for Ara

Ask your AI assistant how your fleet is doing

The DataRemote MCP connects Claude, Cursor, VS Code and other AI assistants to the devices on your Ara account — so the questions you used to call us with get answered in plain language: which unit is offline, why, and what to do about it.

  • Read-only by default
  • Runs on your own computer
  • 8 supported models

Animated illustration: a question typed into an AI assistant passes through the DataRemote MCP to DataRemote Ara, which reaches fleet, telemetry, diagnostic or configuration data, and the answer appears in the assistant. Use the example buttons below it to switch questions or pause the animation.

Your AI assistant

Read-only

Which devices in my Southeast collection are offline?

DataRemote Ara · Fleets & collections

Southeast collection

Devices
48
Online
45
Offline
3
  • 90X200001187offline 2 h
  • 90X200004410offline 35 min
  • 90X200002903offline 6 h

Illustrative example. Serial numbers, collection names and readings are not from real devices.

Works with

ClaudeCursorVS CodeAny MCP client

What it is

What is the DataRemote MCP?

A Model Context Protocol server for DataRemote Ara, DataRemote’s device management platform — and a safe, read-only window into your fleet for the AI assistant your team already uses.

Ask about collection statistics, model and firmware, online status, alarms, LTE signal, power and battery, FXS line registration, settings and logs, and get answers by asking instead of navigating screens. Faster data retrieval, faster decisions and faster troubleshooting across the whole fleet — and the foundation for future DataRemote features, built with the same commitment to protecting your data.

Read the October 7, 2026 launch announcement

At a glance

Read-only by default
Works with
Claude · Cursor · VS Code and any MCP client
Devices
8 models 90X series, VAB-1, CDS series, DRI-9080
Runs on
Your computer Python 3.10 or later
Default mode
Read-only Changes are switched on in settings, never from chat
Permissions
Your account’s Only what your credentials allow
Source code
Available To DataRemote customers

How it works

Ask in plain language. Get answers directly from devices.

Your question travels from the assistant on your screen, through DataRemote Ara, to the device in the field — and the answer comes straight back.

Diagram: your AI assistant connects through the DataRemote MCP on your computer to Ara and your DataRemote devices, so you can ask for a device’s configuration and cell signal summary in plain language. The MCP is read-only by default.
  1. 01

    Your AI assistant

    Claude, Cursor, VS Code and others. You ask in plain language.

  2. 02

    DataRemote MCP

    Runs on your own computer and turns your question into requests to DataRemote’s API.

  3. 03

    DataRemote Ara

    DataRemote’s device management platform, where your account and devices already live. The MCP talks to Ara, never to devices directly.

  4. 04

    Your devices

    Report their status, telemetry, logs and configuration back through Ara.

Example questions

Questions your assistant can now answer

No query language, no parameter paths to memorize. Copy one, or type the question the way you’d ask a colleague.

See whole groups of devices at once, browsed the way you organize them in Ara — by organization, region and site.

  • What collections do I have, and how many devices are offline in each?
  • List the devices in my Southeast collection.
  • Which devices in my Southeast collection are offline?
  • Which collections is 90X200001234 in?

Questions marked Changes on change a device, so they work only after changes have been switched on in the MCP’s settings. Serial numbers and collection names are examples.

What you can do

Fleet operations, from the conversation

Fewer screens and fewer support calls. More answers, from the tool already open on your desk.

  • Status and telemetry built for POTS replacement

    Model, firmware, online state and last contact — plus a live communication test that tells a device that’s answering from one that only looks online. Then CPU, memory, uptime, load, power and battery, LTE signal quality (RSRP, RSRQ and SINR, banded by quality), SIM state, per-interface errors and drops, and FXS registration in one sweep. A performance summary marks each reading normal, warning or critical against the thresholds it lists. Battery health estimates are available on the 90X1 and 90X2.

  • Use the AI assistant you already have

    Nothing new to learn, and no new account — it uses your existing DataRemote sign-in.

  • Fleets and collections at a glance

    Browse your collections by organization, region and site, see online and offline counts, list the devices in each, and look up which collections a device belongs to.

  • Diagnostics in one ask

    Run a full diagnosis, check alarms, and search syslogs with patterns like error|fail|timeout. Open a debug snapshot — kernel messages, network configuration, syslog, hardware and power status — and see a device’s history of power failures, disconnects, reboots and firmware upgrades.

  • Every setting, in plain language

    Describe a setting — a hook-flash time, how a phone port is configured — and the MCP finds it in the device’s parameter tree and reads the value. No paths to memorize.

  • For partners and integrators

    Yours to run, read and adapt

    Run it on your own systems, read and adapt the code — and use it to deliver device management services to your own customers, subject to your agreement with DataRemote.

Answers you can trust

It tells you what it doesn’t know

A made-up zero looks exactly like a real one. So the DataRemote MCP never fills a gap: a reading the device didn’t send is reported as unknown, and your assistant is told so.

Unknown, never zeroOlder models don’t report every counter. Missing values come back flagged, and performance summaries list them for your attention instead of passing them.
No false all-clearsA diagnosis reports problems on the evidence for them, and an all-clear only as far as its checks could run — with a list of what was read and evaluated.
Labelled when it isn’t liveA single-setting read may come from a cache up to five minutes old, and says so with its age; reading several settings at once never uses it. Logs and snapshots are reused within a session until you ask for a fresh copy.
Offline means offlineAn offline device can’t be diagnosed, so the assistant tells you it’s offline and when it was last seen — instead of guessing at its state.

Same device · same missing reading

A tool that guesses

Battery
0%
Health
normal

Looks like a dead battery on a healthy device. Neither is true.

DataRemote MCP

Battery
unknown
Health
incomplete

Says the device didn’t report it, and which checks couldn’t run.

Illustrative comparison, not output from a real device.

Safe by default

Your assistant can look. Changing anything is your call.

Out of the box, the DataRemote MCP reads but can’t change anything — on a device or in your account. So an assistant can’t reboot an alarm panel’s line, or move a device out of its collection, by accident.

  • Your account’s permissions. It can do only what your DataRemote credentials allow, and only through the actions it offers.
  • The switch is yours. Changes are turned on in the MCP’s settings on your computer — never from inside a conversation.
  • Runs on your computer. Not a hosted service you have to trust blind — and the source is there to read.
  • Always know which mode you’re in. Ask “Can you make changes right now?” and the MCP reports whether change tools are available — and names the ones it’s withholding.
  1. Available from the start

    Look

    Status, telemetry, settings, logs, snapshots, diagnostics and configuration backups. Reading never changes a device.

  2. Off until you switch it on

    Change

    Reboots, setting changes, configuration uploads, applies and restores, and firmware updates — plus account changes such as moving devices between collections. Until you switch changes on in the MCP’s own settings, these actions are hidden from your assistant entirely, and nothing said in a conversation can turn them on.

  3. Serial check first

    Factory reset or firmware update

    Even with changes on, these two must be explicitly confirmed in the request, and your assistant is expected to confirm the device serial with you before sending it.

Security and safeguards

Built for your IT security review

The details your security team will ask about, answered before they ask.

  • Credentials

    Passwords out of plain text

    Optional 1Password integration resolves your credentials as the server starts, so the password is never written to disk.

  • Sign-in

    Encrypted sign-in only

    The MCP refuses to send your password to DataRemote’s API over an unencrypted connection.

  • Prompt safety

    Device text treated as data

    Log lines, snapshot files and names reported by devices arrive with a notice marking them as untrusted, so your assistant knows to treat them as data, not instructions.

  • Commands

    Queued isn’t done — and never doubled

    Reboot, reset and firmware commands come back as queued, with an ID. Ask “did the reboot finish?” and the MCP checks whether the device actually carried it out. A request that times out is reported as unknown and never resent automatically, so it can’t be queued twice.

  • Restore

    Restores take a safety backup first

    Before restoring, the MCP backs up the device’s current configuration and stops if that fails. A backup goes back only onto the device it came from unless you explicitly allow otherwise, and one altered since it was saved is always refused.

  • Encryption

    Encrypted configurations stay sealed

    The MCP never decrypts anything. Each backup is saved with a record of its device, model, firmware and checksum, readable only by you and never overwritten unless you ask. On 90X and VAB-1 devices, credential fields arrive sealed by the device.

Get started

From request to first answer in four steps

  1. 01

    Get the MCP

    It’s offered to DataRemote customers. Contact us or your Tier 3 support representative.

  2. 02

    Install it

    It installs on your computer with Python’s standard package tools and needs Python 3.10 or later.

  3. 03

    Add your sign-in

    Use your existing DataRemote account. Keep the password in a manager such as 1Password if you’d rather it never touched disk.

  4. 04

    Connect and ask

    Register it with Claude Desktop, Cursor, VS Code or another MCP client, then ask about your devices in plain language.

Your first session

Six questions that change nothing

A short, read-only tour of what your assistant can do. Run them in order on day one.

  1. 1 Can you make changes right now, or are you read-only?
  2. 2 What collections do I have, and how many devices are offline in each?
  3. 3 Pick an online device from my Southeast collection and tell me its model, firmware and uptime.
  4. 4 Give me a performance summary for 90X200001234. Anything that needs attention?
  5. 5 Search its syslog for errors in the recent log and summarize what you find.
  6. 6 Back up its configuration to my backups folder.

Already using it? Send questions and issues to [email protected].

DataRemote MCP frequently asked questions

What is the DataRemote MCP?
The DataRemote MCP is a Model Context Protocol server for DataRemote Ara, DataRemote’s device management platform. It lets an AI assistant such as Claude, Cursor or VS Code answer questions about the DataRemote devices on your account — collection statistics, model and firmware, online status, alarms, LTE signal, power and battery, FXS line registration and more — and read settings, search syslogs, pull debug snapshots, run diagnostics and back up configurations.
What is the Model Context Protocol (MCP)?
The Model Context Protocol is an open standard that lets AI assistants connect to outside tools and data. An assistant that supports MCP can use the DataRemote MCP to reach your devices through DataRemote Ara, so you can ask about them in plain language instead of navigating screens.
Which AI assistants work with the DataRemote MCP?
Any AI assistant or client that supports the Model Context Protocol can connect, including Claude, Cursor and VS Code.
Which DataRemote devices does it support?
The DataRemote MCP supports the 90X1, 90X2, 90X5, VAB-1, DRI-9080, CDS-9010, CDS-9070 and CDS-9090. Older models don’t report every reading; when a value isn’t available, the MCP says so instead of guessing. Battery health estimates are available on the 90X1 and 90X2.
Can the AI assistant change my devices?
Not by default. Reboots, setting changes, configuration uploads, applies and restores, firmware updates and account changes such as collection membership are hidden from the assistant until changes are switched on in the MCP’s own settings — nothing said in a conversation can turn them on. Even then, a factory reset or firmware update must be explicitly confirmed in the request, after your assistant checks the device serial with you. Not sure which mode you’re in? Ask “Can you make changes right now?” and it will tell you, naming any tools that are withheld. See how the controls work.
What happens when a device doesn’t report a reading?
It’s reported as unknown, never as zero. Diagnostics follow the same rule: if a check couldn’t run, the result says “unknown” or “incomplete” rather than “normal”, along with a list of what was actually read and evaluated. Why this matters.
What can’t the DataRemote MCP do?
It can’t reach devices directly — everything goes through DataRemote’s API, and it sees only what that API exposes. It can’t go beyond your account’s devices and permissions, change anything while changes are switched off, decrypt a sealed configuration, or invent a reading a device didn’t send. It also can’t diagnose an offline device: it tells you the device is offline and when it was last seen.
Where does the DataRemote MCP run, and how does it reach my devices?
It runs on your own computer and talks to DataRemote’s API in Ara — never to devices directly. It acts with your account’s permissions, so it can do only what your credentials allow. Answers about your devices are returned to the AI assistant you choose, so your organization’s policies for that assistant apply.
How are my DataRemote credentials stored?
You choose. Credentials can come from your environment, a local settings file, or a password manager: with the optional 1Password integration, the password is resolved when the server starts and never written to disk. Sign-in is refused over an unencrypted connection.
Can partners use it to manage their customers’ devices?
Yes. Subject to your agreement with DataRemote, you can run the MCP on your own systems to manage DataRemote devices and accounts you are authorized to access — including to deliver device management services to your own customers. What you can’t do is charge for the MCP itself, include it in a product or service you sell, or offer others hosted access to it. Contact DataRemote about other arrangements.
Is the source code available?
Yes, to DataRemote customers. You can read and adapt the code and run it on your own computer. The device parameter reference and device knowledge notes that ship with it remain DataRemote proprietary data, for use with the MCP only.
Does the DataRemote MCP replace Ara or the Ara API?
No. The MCP works through your Ara account. Ara remains the device management platform, and its interface and API remain available for provisioning, monitoring and integration work.
How do I get the DataRemote MCP?
Contact DataRemote or your Tier 3 support representative. Existing users can send questions and issues to [email protected].

Put your fleet one question away

Contact [email protected] or your Tier 3 support representative to get the DataRemote MCP for your Ara account.