Labsco
MCP SERVER

TagoIO

by tago-io ↗

Work on a TagoIO account by asking — read devices and data, debug a failing analysis, build a dashboard from a description.

Network, Endpoint & Fleet Management
Summary
The debugging loop is the reason to install it.

Reading a device list is table stakes. What is unusual here is that the analysis console, the script upload and the single test run are all reachable from the same conversation, so "why did the daily report fail" ends with a fix that ran, not with a stack trace you go paste somewhere. Token choice is the real access decision: a Profile Token reaches your whole profile, while an Analysis token is scoped by IAM and is the one that belongs in a shared or production setup.

What it is

TagoIO's own server for its IoT platform. Your assistant reads devices, data, dashboards and analyses, and makes the changes you ask for, from your IDE or chat client.

What you get
  • Fleet work: list devices, find the ones that stopped sending, read recent records from a device, create a device on a network and get its token
  • Debugging without tab-switching: read an analysis console to find out why last night's run failed, upload the fixed script, and run it once to confirm
  • Dashboard building from a description — a map of units, a temperature line chart, a card for battery level — and comparing a widget's configuration against the variables a device actually sends
  • Permissions: work out which policy an analysis needs to write to an entity, and list every access policy touching TagoRUN users
  • Account housekeeping: check how close you are to a data-records limit, or find and delete stored files by age and size
  • Official code examples for payload parsers, found and adapted to your device
  • Writes go through your client's confirmation flow, so deletes, credential rotation and script uploads are approved before they land
Requirements

A TagoIO Profile Token from your profile settings, and the hosted server at https://mcp.ai.tago.io. Requests go to US East by default; set an `x-tagoio-region` header to `eu-w1`, or to a full API endpoint for a dedicated TagoDeploy instance. Analysis and Device tokens work too, with correspondingly narrower reach. To run it yourself, the npm package @tago-io/mcp-server, version 4.0.0, over npx with TAGOIO_TOKEN; over stdio there are no headers, so set TAGOIO_API instead.

Setup effort

One command plus a key — npx -y @tago-io/mcp-server, then supply credentials