Tago Io

io.github.tago-io由 GitHub 账号 tago-io 发布v2.1.3更新于 Oct 27, 2026

Model Context Protocol server for TagoIO data and analytics

已验证STDIO仅桌面云端与基础设施开发者工具数据与分析

概览

AI 生成的概览

面向 TagoIO 物联网账户的 MCP 服务器，让助手读取设备、数据、仪表盘和分析，并按请求做出修改。

可以做什么
  • 搜索、创建、更新和删除设备、实体、动作、分析与仪表盘
  • 读取、发送、编辑和删除设备与实体的数据记录
  • 构建并校验仪表盘组件，包括自定义组件代码
  • 运行分析、读取控制台输出、上传或下载脚本
  • 管理 TagoRUN 用户、通知、访问策略与账户配额
  • 检索已存文件、连接器、网络、文档与代码示例
适用场景
当你使用 TagoIO 账户，希望助手在不切换页面的情况下检查设备群、排查分析故障、搭建仪表盘或调整权限与用户时适用。编写载荷解析器或组件时查阅 TagoIO 文档和代码示例也很方便。
运行要求
需要 TagoIO 的 Profile、Analysis 或 Device 令牌：本地 npm 包通过 TAGOIO_TOKEN 提供（需 Node.js 22.12 或更高版本），托管端点则使用 Bearer Authorization 请求头。需能访问 TagoIO API；TAGOIO_API 或 x-tagoio-region 请求头可指定其他区域或专属实例。
安装前请注意
该服务器既读也写：可删除设备、数据、文件、用户和策略，轮换凭据并上传脚本，请依赖客户端的确认流程。Profile 令牌可访问整个账户，共享或生产环境宜改用 Analysis 或 Device 令牌。若不自行本地运行，令牌会发送到 TagoIO 托管端点。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Tago Io，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README


[TagoIO]

TagoIO | MCP Server

Work on your TagoIO account by asking. Your AI assistant reads your devices, data, dashboards, and analyses, and makes the changes you ask for, from your IDE or chat tool.

[Install in VS Code] [Install in VS Code Insiders] [Install in Visual Studio] [Install in Cursor] [Add to LM Studio]

Start here

  1. Get a token. Generate a Profile Token in TagoIO Profile Settings.
  2. Add the server to your client. Use an install button above, or copy the config for your tool from Client setup.
  3. Ask something. Try: "List my devices and tell me which ones stopped sending data this week."

Your client connects to the TagoIO hosted server at https://mcp.ai.tago.io. You can also run the server yourself.

What you can ask for

The server gives your assistant around 80 focused capabilities across your account. You describe the outcome, and it picks the tools. Some things that work well today:

Understand your fleet

  • "Which devices haven't sent data in the last 7 days?"
  • "Show me the last 50 records from Water Meter 12 and summarize the flow variable."
  • "Create a device on my LoRaWAN network, then give me its token."

Debug without tab-switching

  • "The Daily Report analysis failed last night. Read the console and tell me why."
  • "Fix the bug you found, upload the script, and run it once to confirm."
  • "A customer says their dashboard is empty. Log in as that user and check what they see."

Build dashboards from a description

  • "Build a dashboard for my cold chain fleet: a map of the units, a temperature line chart for the last 24 hours, and a card for battery level."
  • "This gauge shows no value. Compare its configuration to the variables the device actually sends."

Untangle permissions

  • "My analysis gets a permission error writing to the Sites entity. What policy does it need?"
  • "Show me every access policy that touches TagoRUN users."

Keep the account tidy

  • "How close am I to my data records limit this month?"
  • "Find stored files older than a year and larger than 5 MB, then delete them."

Write code with the docs in context

  • "Find the official example for parsing a Dragino LHT65 payload and adapt it to my device."

The server reads and writes. Deleting data, rotating credentials, and uploading scripts run through your assistant's confirmation flow, so you approve each change before it lands.

Client setup

Each config below points at the hosted server. Replace YOUR-TAGOIO-TOKEN with your Profile Token.

ClientWhere the config lives
VS Code / GitHub Copilot.vscode/mcp.json or User Settings
Claude Codeclaude mcp add-json CLI
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows)
Cursor~/.cursor/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
JetBrains IDEsSettings > Tools > AI Assistant > MCP
Google Gemini CLI~/.gemini/settings.json
Amazon Q CLI~/.aws/amazonq/mcp.json
Warp~/.warp/mcp.json
Kiro.kiro/mcp.json
OpenAI Agents / ChatGPTAgent Builder UI

VS Code / GitHub Copilot

Add to .vscode/mcp.json for one project, or to User Settings for all of them. VS Code Insiders takes the same config, and Copilot reads the same file.

json
{  "servers": {    "@tago-io/mcp": {      "type": "http",      "url": "https://mcp.ai.tago.io",      "headers": {        "Authorization": "Bearer ${input:tagoToken}"      }    }  },  "inputs": [    {      "type": "promptString",      "id": "tagoToken",      "description": "TagoIO Profile Token",      "password": true    }  ]}

Claude Code

bash
claude mcp add-json tagoio '{"type":"http","url":"https://mcp.ai.tago.io","headers":{"Authorization":"Bearer YOUR-TAGOIO-TOKEN"}}'

Claude Desktop

Connect through the mcp-remote bridge.

json
{  "mcpServers": {    "@tago-io/mcp": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.ai.tago.io",        "--header",        "Authorization: Bearer YOUR-TAGOIO-TOKEN"      ]    }  }}

Cursor

json
{  "mcpServers": {    "@tago-io/mcp": {      "url": "https://mcp.ai.tago.io",      "headers": {        "Authorization": "Bearer YOUR-TAGOIO-TOKEN"      }    }  }}

Windsurf

json
{  "mcpServers": {    "@tago-io/mcp": {      "serverUrl": "https://mcp.ai.tago.io",      "headers": {        "Authorization": "Bearer YOUR-TAGOIO-TOKEN"      }    }  }}

JetBrains IDEs

Open Settings > Tools > AI Assistant > Model Context Protocol (MCP), add a server, and paste:

json
{  "servers": {    "@tago-io/mcp": {      "url": "https://mcp.ai.tago.io",      "requestInit": {        "headers": {          "Authorization": "Bearer YOUR-TAGOIO-TOKEN"        }      }    }  }}

Google Gemini CLI

json
{  "mcpServers": {    "@tago-io/mcp": {      "httpUrl": "https://mcp.ai.tago.io",      "headers": {        "Authorization": "Bearer YOUR-TAGOIO-TOKEN"      }    }  }}

Amazon Q CLI

json
{  "mcpServers": {    "@tago-io/mcp": {      "url": "https://mcp.ai.tago.io",      "headers": {        "Authorization": "Bearer YOUR-TAGOIO-TOKEN"      }    }  }}

Warp

Connect through the mcp-remote bridge.

json
{  "mcpServers": {    "@tago-io/mcp": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.ai.tago.io",        "--header",        "Authorization: Bearer YOUR-TAGOIO-TOKEN"      ]    }  }}

Kiro

Connect through the mcp-remote bridge, in .kiro/mcp.json at your project root.

json
{  "mcpServers": {    "@tago-io/mcp": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.ai.tago.io",        "--header",        "Authorization: Bearer YOUR-TAGOIO-TOKEN"      ]    }  }}

OpenAI Agents / ChatGPT

In Agent Builder or ChatGPT MCP settings:

  • Server URL: https://mcp.ai.tago.io
  • Protocol: Streamable HTTP
  • Authentication: Authorization: Bearer YOUR-TAGOIO-TOKEN header

Choosing a token

TokenWhere to get itWhat it reaches
ProfileProfile SettingsYour whole profile. Start here.
AnalysisAnalysis > your analysis, set to run "External"Only what that analysis can reach. Fits shared and production environments where access is controlled through IAM.
DeviceThe device itselfThat device's data. Account-level requests return a permission error.

Regions and endpoints

Requests go to US East by default. Set the x-tagoio-region header to reach a different endpoint:

ValueTarget
us-e1US East (default)
eu-w1EU West
https://api.your-instance.ioYour dedicated TagoDeploy instance
x-tagoio-region: eu-w1

For TagoDeploy, pass your instance's full API endpoint over https://. This works on the hosted server, so a dedicated instance needs the same one-line config as a public region.

Over STDIO there are no headers. Set TAGOIO_API to your endpoint instead.

Run it locally

Run the server on your own machine for offline work, or when your network blocks outbound connections. Install Node.js 22.12 or newer, then:

bash
npx -y @tago-io/mcp-server        # STDIO, what desktop apps and IDEs expectnpx -y @tago-io/mcp-server http   # HTTP on port 3000

STDIO reads the token from the environment:

json
{  "mcpServers": {    "@tago-io/mcp": {      "command": "npx",      "args": ["-y", "@tago-io/mcp-server"],      "env": {        "TAGOIO_TOKEN": "YOUR-TAGOIO-TOKEN"      }    }  }}

For Claude Code:

bash
claude mcp add @tago-io/mcp-server -e TAGOIO_TOKEN=YOUR-TAGOIO-TOKEN -- npx -y @tago-io/mcp-server

HTTP mode takes the token per request, so several people can share one server with their own credentials. Set the port with MCP_PORT, and check GET /health to confirm the server is up. To point any config in this README at your local server, swap the URL for http://localhost:3000. Run npx -y @tago-io/mcp-server --help for the full option list.

Writing custom widgets

Custom widgets are React components with a strict authoring contract: a provider wrapper, pinned npm: dependencies, a // tailwind marker. The server validates your code against that contract and reports what breaks it.

The custom widget skill teaches the contract itself, with worked examples. Install it for Claude Code:

bash
# all projectsmkdir -p ~/.claude/skills/custom-widget-developmentcurl -fsSL https://raw.githubusercontent.com/tago-io/mcp-server/master/skills/custom-widget-development/SKILL.md \  -o ~/.claude/skills/custom-widget-development/SKILL.md
# one projectmkdir -p .claude/skills/custom-widget-developmentcurl -fsSL https://raw.githubusercontent.com/tago-io/mcp-server/master/skills/custom-widget-development/SKILL.md \  -o .claude/skills/custom-widget-development/SKILL.md

For other clients, put the same file wherever that client loads skills or reusable prompts from.

Your token and your data

The server strips your token from every result, error, script download, and console output before it reaches your assistant. Environment variable values, minted analysis tokens, and signed file URLs get the same treatment.

Some settings stay in the TagoIO admin: TagoRUN environment configuration, SSO and custom domains, test emails, and anonymous user creation.

Troubleshooting

It won't connect. Confirm the token is still valid and that https://mcp.ai.tago.io is reachable from your network. If your account lives in EU West, set the x-tagoio-region header.

Authentication error. Over HTTP the header reads Bearer YOUR-TOKEN, with the space. Over STDIO the token goes in TAGOIO_TOKEN. If the format checks out, the token may lack permission for what you asked.

A request comes back empty. Two usual causes: the device has no data in the window you asked about, or your profile lacks access to that device.

The bridge fails (Claude Desktop, Warp, Kiro). Check for Node.js 22.12 or newer, then run the bridge by hand to read the real error:

bash
npx -y mcp-remote https://mcp.ai.tago.io --header "Authorization: Bearer YOUR-TOKEN"
Full tool reference

Every tool the server exposes, grouped by domain. Each one carries its own parameters, limits, and read or write annotation in the description your client reads.

DomainTools
Devicessearch_devices, get_device, create_device, update_device, delete_device, configure_device
Device dataread_device_data, send_device_data, edit_device_data, delete_device_data
Actionssearch_actions, get_action, create_action, update_action, delete_action
Analysessearch_analyses, get_analysis, create_analysis, update_analysis, delete_analysis, upload_analysis_script, download_analysis_script, run_analysis, read_analysis_console
Dashboards & widgetssearch_dashboards, get_dashboard, create_dashboard, update_dashboard, delete_dashboard, get_widget, create_widget, update_widget, delete_widget, widget_schema_lookup, validate_widget_configuration, get_custom_widget_code, upload_custom_widget_code
Entitiessearch_entities, get_entity, create_entity, update_entity, delete_entity, update_entity_schema
Entity dataread_entity_data, send_entity_data, edit_entity_data, delete_entity_data, empty_entity_data
Run userssearch_run_users, get_run_user, create_run_user, update_run_user, delete_run_user, login_as_run_user
Run-user notificationsread_run_user_notifications, send_run_user_notification, update_run_user_notification, delete_run_user_notification
Filessearch_files, delete_files
Access managementsearch_access_policies, get_access_policy, lookup_access_permissions, create_analysis_access_policy, create_run_user_access_policy, update_analysis_access_policy, update_run_user_access_policy, delete_access_policy
Profileget_profile, get_profile_limits, get_profile_statistics, search_secrets
Connectors & networkssearch_connectors, get_connector, search_networks, get_network
Docs & examplesplatform_overview, search_docs, read_doc, search_code_examples, get_code_example

Contributing

Issues and pull requests are welcome. Agent instructions live in AGENTS.md.

License

MIT. See the LICENSE file.

Built by the TagoIO team. Need a hand? Check the TagoIO documentation or contact support.

来源：README.md，提交 3705461

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v2.1.3最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。