ScreenTapDocs
PricingSupportBack to site

Getting started

  • How it works
  • Installation
  • First-time setup

Connect your agent

  • Overview
  • Claude Code
  • Claude Desktop
  • Cursor
  • Codex
  • Windsurf
  • VS Code
  • Gemini CLI
  • Other clients

Using ScreenTap

  • Giving tasks
  • Tools

Account

  • License & billing
  • Privacy

Help

  • Troubleshooting
Docs / Other clients⌄

Getting started

  • How it works
  • Installation
  • First-time setup

Connect your agent

  • Overview
  • Claude Code
  • Claude Desktop
  • Cursor
  • Codex
  • Windsurf
  • VS Code
  • Gemini CLI
  • Other clients

Using ScreenTap

  • Giving tasks
  • Tools

Account

  • License & billing
  • Privacy

Help

  • Troubleshooting
← PreviousGemini CLINext →Giving tasks

Connect your agent

Other MCP clients

Anything that speaks MCP, over HTTP or stdio.

  1. 1

    Pick the transport your client supports

    ScreenTap offers both. Use HTTP if your client can connect to a URL, and stdio if it can only start a program.

    Connection details
    Streamable HTTP   http://127.0.0.1:47811/mcp
    stdio             /Applications/ScreenTap.app/Contents/MacOS/ScreenTap --stdio
  2. 2

    HTTP clients

    Most take a JSON entry with a url. The field name varies by client (url, serverUrl or httpUrl).

    HTTP
    {
      "mcpServers": {
        "screentap": { "url": "http://127.0.0.1:47811/mcp" }
      }
    }
  3. 3

    stdio clients

    Point the client at the ScreenTap app with the --stdio argument.

    stdio
    {
      "mcpServers": {
        "screentap": { "command": "/Applications/ScreenTap.app/Contents/MacOS/ScreenTap", "args": ["--stdio"] }
      }
    }

Good to know

  • The client has to run on the same Mac as ScreenTap: the server only listens on 127.0.0.1.
  • Keep the ScreenTap app open in both cases.

Not working?

Check that the ScreenTap app is open and your iPhone is connected, then restart your agent or start a new session. More fixes in Troubleshooting.