OpenClaw uses a CLI-first, skills-based approach — no MCP needed. TapKit fits naturally into this model.
Why OpenClaw + TapKit — OpenClaw’s philosophy is “install capabilities, not servers.” TapKit skills teach the agent how to use the tapkit CLI — no protocol adapters, no persistent MCP servers. The agent just calls shell commands.
Setup
Install TapKit skills from ClawHub:
clawhub install tapkit
# Installing tapkit skills...
# ✓ tapkit/core → ~/.openclaw/skills/tapkit/
# ✓ tapkit/hinge → ~/.openclaw/skills/hinge/
# ✓ tapkit/telegram → ~/.openclaw/skills/telegram/
# ✓ tapkit/tiktok → ~/.openclaw/skills/tiktok/
# ✓ tapkit/linkedin → ~/.openclaw/skills/linkedin/
# ✓ tapkit/uber-eats → ~/.openclaw/skills/uber-eats/
#
# Requires: tapkit CLI (detected ✓)
Usage
The killer feature: control your iPhone from any messaging channel — WhatsApp, Telegram, Slack, etc.
you (WhatsApp): Hey, order me a burrito from Chipotle on Uber Eats
openclaw: On it. Let me open Uber Eats and find Chipotle...
[runs: tapkit open "Uber Eats"]
[runs: tapkit screenshot --base64]
I can see the Uber Eats home screen. Searching for Chipotle...
[runs: tapkit tap 207 120] ← search bar
[runs: tapkit type "Chipotle"]
...
Skills requirement — OpenClaw’s requires.bins metadata ensures the agent only loads TapKit skills when the tapkit CLI is installed. If you haven’t installed the CLI, the skills won’t appear.
