iot-platform_skill

This skill helps you connect to OpenClaw MCP API, configure gateway connections, and manage devices and channels from the Cloud Studio environment.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill iot-platform

  • _meta.json287 B
  • SKILL.md4.0 KB

Overview

This skill is a practical guide to connect to Cloud Studio IoT's OpenClaw platform via the MCP (Model Context Protocol) API. It documents how to verify and configure the OpenClaw gateway, add an MCP server entry for clients like Claude Code, and use the gateway to interact with devices and channels. The guide is focused on configuration steps, gateway modes, available MCP tools, and troubleshooting tips.

How this skill works

The gateway exposes an MCP server endpoint (SSE) that MCP clients can register in their settings to gain programmatic access to OpenClaw resources. Once configured, the gateway presents tools and resources such as device lists, sensor reads, channel management, and command execution over URIs like openclaw://devices. The guide explains local loopback and Tailscale binding modes, plus authentication options for public access.

When to use it

  • Setting up an MCP client (e.g., Claude Code) to control OpenClaw devices
  • Sending commands to IoT devices or running agent tasks on the gateway
  • Reading live sensor data or enumerating device/ channel resources
  • Configuring remote access via Tailscale (serve or funnel modes)
  • Troubleshooting gateway connectivity, ports, or authentication

Best practices

  • Verify gateway health with curl http://127.0.0.1:18789/healthz before adding MCP entries
  • Use loopback binding for local-only development and Tailscale serve/funnel for remote access
  • Store funnel mode passwords securely and keep gateway auth config synchronized with MCP client settings
  • Restart the gateway and monitor journalctl logs when encountering connectivity issues
  • Test MCP tooling visibility in your client after changing mcpServers settings and restarting the client

Example use cases

  • Add the openclaw MCP server to Claude Code to expose device and sensor tools within the client
  • Issue an actuator command to a specific device using openclaw_device_command from an MCP client
  • Poll openclaw://devices/{id}/sensors to ingest telemetry into a monitoring workflow
  • Send notifications through configured channels (e.g., Telegram) using openclaw_channel_send
  • Run maintenance or automation tasks on the gateway with openclaw_agent_run

FAQ

Use the loopback URL http://127.0.0.1:18789/mcp and restart your client so the OpenClaw tools appear.

How do I enable remote access over Tailscale?

Set gateway tailscale.mode to serve or funnel in the gateway config, ensure Tailscale is connected, and update the MCP URL to your Tailscale device host.

What if the gateway refuses connections?

Confirm gateway health, check port availability (ss -tlnp | grep 18789), restart the gateway service, and review journalctl logs for errors.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational