Skip to main content
The TapKit plugin for Claude Code gives Claude iPhone control in your terminal. It installs an MCP server connection and TapKit skills that teach Claude how to use the tools and navigate supported apps.

Step 1: Add the TapKit plugin marketplace

Run this command in Claude Code:

Step 2: Install the TapKit plugin

  1. Type /plugin and navigate to the Marketplaces tab (press the right arrow key twice).
  2. Select the tapkit-plugins-claude marketplace and hit enter.
  3. Go to Browse Plugins, hit enter.
  4. Find tapkit, toggle it on, and hit enter to install.
  5. Run /reload-plugins to load the plugin.

Step 3: Authenticate

  1. Type /mcp in Claude Code.
  2. Navigate down to the TapKit entry and select it.
  3. Choose Authenticate — your browser will open to sign in to TapKit.
  4. After signing in, you’ll be redirected back.
  5. Run /exit and restart Claude Code for the changes to take effect.
If your browser doesn’t open automatically, copy the URL from Claude Code and paste it manually. If the redirect fails after signing in, paste the full callback URL from your browser’s address bar back into Claude Code.

Permissions

Claude Code asks for approval before an MCP tool’s first use in the default permission mode. When prompted, you can allow the TapKit tools for future calls, or run /permissions and add mcp__tapkit__* to your allow rules. Leave the default prompts in place if you want to confirm phone actions individually.

Verify it works

If a phone is connected via the Mac app, you’ll see the screenshot.

Troubleshooting

Make sure the TapKit Mac app is running with a phone connected. Run /mcp to check the connection status. You may need to re-authenticate.
Check that your phone is awake, unlocked, and still connected. If the Mac app shows the phone as disconnected, unplug and reconnect the USB cable.
If you have multiple phones, Claude may need to select the right one. Ask Claude to “list my available phones” and then specify which one to use.
Run /mcp, select TapKit, and choose to re-authenticate. Make sure you’re signed into the correct TapKit account in your browser.