Skip to main content
For anything that doesn’t have an official TapKit plugin, you can connect directly using our MCP server. This works with Cursor, Windsurf, custom agents, and any other tool that supports the Model Context Protocol.

MCP server URL

Adding the MCP to your client

Most MCP clients accept a JSON configuration like this:
Where you add this depends on your client:
  • Cursor — add to your MCP settings in Cursor’s configuration
  • Windsurf — add to the MCP configuration file
  • Custom clients — point your MCP client at the URL above

Authentication

When your client first connects to the TapKit MCP server, you’ll be prompted to authenticate via your browser. Sign in with your TapKit account and the token will be cached for future sessions.

How it works

The MCP server runs as a hosted endpoint at mcp.tapkit.ai. You don’t need to run anything locally beyond the TapKit Mac app with a connected iPhone. Your MCP client connects to the server, which routes commands to the Mac app, which executes them on the phone. Screenshots are returned through the same channel.

Available tools

Once connected, your client has access to all TapKit tools: