メニュー
Use when configuring, verifying, or explaining the Wendy CLI MCP server for AI assistants with `wendy mcp setup` or `wendy mcp serve`, especially Claude Code, Claude Desktop, Codex, or device-tool access.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Expert guidance on building and deploying apps to WendyOS edge devices. Use when developers mention: (1) Wendy or WendyOS, (2) wendy CLI commands, (3) wendy.json or entitlements, (4) deploying apps to edge devices, (5) remote debugging Swift on ARM64, (6) NVIDIA Jetson or Raspberry Pi apps, (7) cross-compiling Swift for ARM64.
Use when creating, reviewing, or debugging `wendy.json` entitlements for Wendy apps, especially device access, networking, persistence, GPU, audio, camera, Bluetooth, USB, I2C, GPIO, SPI, serial, input, or MCP devices.
Use when creating, validating, or repairing a Wendy project scaffold, adapting Wendy templates, `wendy.json`, JSON schema setup, or project entitlements with `wendy init`, `wendy json`, or `wendy project entitlements`.
Use when a developer wants to build, deploy, run, detach, stream logs, start, stop, list, remove, or clean up Wendy apps with `wendy build`, `wendy run`, `wendy device apps list`, `wendy device logs`, telemetry streams, or volumes.
Use when a developer or coding agent needs Wendy CLI-native device operations: discover devices, set defaults, inspect device version/system/hardware/WiFi state, update the agent, or gather evidence before SSH/debugging.
Use when working in Wendy Labs repos, especially wendy-agent, WendyOS, samples, templates, or cloud docs, and the task needs orientation on Wendy CLI, agent, gRPC, runtime, or app deployment paths.
| name | wendy-mcp-setup |
| description | Use when configuring, verifying, or explaining the Wendy CLI MCP server for AI assistants with `wendy mcp setup` or `wendy mcp serve`, especially Claude Code, Claude Desktop, Codex, or device-tool access. |
Use this when a developer wants AI assistants to access Wendy device tools through the Wendy CLI MCP server.
Verify the CLI first:
wendy --version
wendy --json info
If the MCP server should connect to a device on startup, either set a default device or use --device when launching the server:
wendy discover --json --timeout 5s
wendy device set-default <hostname>
wendy device get-default
Run this only when the user wants Wendy MCP written into local AI tool configuration:
wendy mcp setup
Current setup behavior configures Claude Code and Claude Desktop when detected. It writes a stdio MCP server entry that runs the installed wendy binary with:
wendy mcp serve
After setup, restart or reload the target AI tool so it discovers the new MCP server.
The MCP server is stdio-based and is normally launched by an MCP host:
wendy mcp serve
wendy mcp serve --device <hostname>
--device can also be written as -d. If omitted, the server attempts to use the configured default device.
For Codex or any MCP host not covered by wendy mcp setup, configure a stdio server named wendy with command wendy and args ["mcp", "serve"]. Add --device <hostname> only when the user wants that MCP server pinned to one device.
Before blaming MCP, verify device access directly with wendy-device-ops:
wendy --json device version --device <hostname>
wendy --json device hardware list --device <hostname>
If wendy mcp serve logs a warning that it could not connect to a device, set a default device or configure the MCP host to launch wendy mcp serve --device <hostname>.
MCP exposes operational device tools to the assistant host. Do not configure it silently. Tell the user what local config file was changed when the CLI reports it, and do not copy tokens, WiFi passwords, or device-specific secrets into reusable docs or issue text.