TagoIO

TagoIO is an MCP server that connects AI assistants directly to your TagoIO IoT cloud account to manage devices, telemetry data, analyses, and platform dashboards. Designed for IoT developers, operations engineers, and system administrators, it provides roughly 80 account-level tools accessible from development environments and chat tools. Users can query telemetry history, identify unresponsive hardware, inspect error logs for backend analysis scripts, and deploy code updates without leaving their editor. The server also supports creating and auditing platform dashboards, inspecting permission policies across entities, tracking monthly data usage against quota limits, and cleaning up legacy storage assets. By exposing hosted HTTP and local STDIO configurations across multiple cloud regions and custom deployments, it enables automated fleet troubleshooting, data visualization setup, and administrative maintenance using plain language instructions through any compatible MCP client interface.

Category: Cloud & Infrastructure

Tags: data analysis, iot, tagoio, telemetry

Visit TagoIO

How to install and configure TagoIO

Follow these steps to connect your MCP client to the hosted TagoIO server: 1. Generate a Profile Token inside your account at Profile Settings. 2. Open your client's MCP configuration file (for example, ~/.cursor/mcp.json in Cursor or claude_desktop_config.json in Claude Desktop). 3. For direct HTTP clients like Cursor, add the server definition: json { "mcpServers": { "@tago-io/mcp": { "url": "https://mcp.ai.tago.io", "headers": { "Authorization": "Bearer YOUR-TAGOIO-TOKEN" } } } } 4. For Claude Desktop, configure the mcp-remote bridge using npx -y mcp-remote https://mcp.ai.tago.io --header "Authorization: Bearer YOUR-TAGOIO-TOKEN" under your mcpServers object. 5. Save the configuration and restart your client to start interacting with your devices.

What you can do with TagoIO

• Identify dormant IoT hardware across the fleet by finding devices that have not transmitted telemetry records over the past seven days. * Troubleshoot failing backend analysis routines by inspecting script execution consoles, applying code fixes, and triggering runs to verify solutions. * Construct custom operational dashboards containing maps, metric gauges, and time-series line charts directly from conversational instructions. * Audit security permissions by reviewing access policies governing users, external runtime analyses, and specific data buckets.

Key facts

• https://github.com/tago-io/mcp-server
• Cloud & Infrastructure, CRM, ERP & E-commerce, Data & Analytics
• data analysis, iot, tagoio, telemetry

Part of MCP Servers

How do I install TagoIO?

Generate a Profile Token in your TagoIO profile settings. Then, add the hosted endpoint https://mcp.ai.tago.io to your client configuration. Tools like Cursor connect directly using HTTP headers, while clients like Claude Desktop run through the npx mcp-remote bridge using Bearer token authorization.

What can TagoIO do?

The server provides about 80 capabilities across your account. It allows AI assistants to query device telemetry, check hardware communication statuses, debug and update analysis scripts, build visual dashboards, inspect IAM access policies, and audit monthly account usage limits.

Which MCP clients work with TagoIO?

It supports VS Code, GitHub Copilot, Cursor, Claude Code, Claude Desktop, Windsurf, JetBrains IDEs, Google Gemini CLI, Amazon Q CLI, Warp, Kiro, and OpenAI Agents via streamable HTTP or standard command bridges.

Can I connect TagoIO to custom deployments or different regions?

Yes. While the server defaults to the US East region, you can pass the x-tagoio-region header set to eu-w1 for EU West or provide the full HTTPS endpoint URL for a private TagoDeploy instance.