SenseCAP PaaS MCP ブリッジ — デプロイガイド

GitHub でソースを見る
プリセット

SenseCAP PaaS MCP Bridge

Deploy a small always-on bridge that connects your SenseCAP PaaS account to a XiaoZhi voice assistant (or any other MCP-compatible host) via the Model Context Protocol.

DevicePurpose
Any Docker host (e.g. reComputer R1100)Runs the MCP bridge container

What you'll get:

  • 9 MCP tools exposed to your voice assistant: get a spoken fleet overview, get a full-channel spoken reading for one device, register a device, look up a device key, read the latest telemetry, list historical telemetry, aggregate chart points, and browse/read Arduino code templates
  • An outbound WebSocket connection to your XiaoZhi MCP access point — no inbound ports, no public exposure
  • Credentials passed in at deploy time only, never baked into the image — update them any time by redeploying

Requirements: Docker installed · A SenseCAP PaaS Access ID/Key (sensecap.seeed.cc → API keys) · A XiaoZhi MCP access point URL from your XiaoZhi console

1

Deploy MCP Bridge

Deploy the bridge container with your SenseCAP PaaS credentials and XiaoZhi MCP endpoint.

デプロイ後

The bridge is now running and connected to your XiaoZhi MCP endpoint.

Try It

  1. Open your XiaoZhi app or device and start a conversation
  2. Ask something like "我的设备现在怎么样" (or in English, "how are my devices doing")
  3. XiaoZhi should call the bridge's get_farm_overview tool and read back how many devices you have and whether any need attention
  4. Then try asking about one device by name, e.g. "大棚气象站现在怎么样" — XiaoZhi should call get_device_reading and read back that device's current readings across every channel

Next Steps

  • Project README — full tool list and manual/stdio usage
  • To rotate credentials, just redeploy this step with the new Access ID/Key or endpoint — no rebuild needed
デプロイ方法

Deploy on the machine you're currently using.

入力が必要な項目（SenseCraft Solution アプリで入力）
  • SenseCAP PaaS Access ID*

    API credential from the SenseCAP PaaS open platform (sensecap.seeed.cc → API keys)

  • SenseCAP PaaS Access Key*

    API secret paired with the Access ID above. Stored only as a deploy-time environment variable, never baked into the image.

  • Device Timezone (optional)

    IANA timezone (e.g. Asia/Shanghai) used when speaking device report times back to you. Leave blank to use the China site's default (Asia/Shanghai) or UTC otherwise — it will never guess a timezone it isn't sure about.

  • XiaoZhi MCP Endpoint*

    The MCP access point URL from your XiaoZhi console (includes an auth token, so treated as a secret)

既定値のある残り 1 項目
  • SenseCAP Site既定値 global
    3 件の選択肢
    • · Global
    • · China
    • · Develop (internal)

    Which SenseCAP PaaS environment to talk to

トラブルシューティング
IssueSolution
Docker not foundInstall Docker Desktop and ensure it is running
Container keeps restartingCheck logs: docker logs sensecraft-data-mcp — usually a wrong Access ID/Key or endpoint URL
XiaoZhi never calls the toolsConfirm the MCP endpoint URL (including the ?token= part) was copied exactly from the XiaoZhi console
Reported times are off by several hoursSet the "Device Timezone" field to your devices' IANA timezone (e.g. Asia/Shanghai) and redeploy. Left blank, the China site defaults to Beijing time and other sites default to UTC — it never guesses.