SimKit MCP

Your agent wrote the code.
Now let it see what the app did.

Claude Code, Cursor and Codex can read your iOS app's requests and responses, mock a failing server, and drive the simulator, all through SimKit on your Mac. Free.

Terminal
npx -y simkit-mcp

Beta Needs SimKit 1.8, which is in beta: choose Beta in the Download menu on the home page. Setup takes three steps.

You

Mock /login to return a 500, relaunch the app and show me what the user sees.

Agent, through SimKit
  • set_mockPOST /login answers 500
  • relaunch_appcom.example.shop restarted
  • wait_for_requestPOST /login finished, 500 from the mock
  • screenshotthe login screen, as the simulator shows it
  • remove_mockback to the real server

The app shows a blank screen on a 500: LoginViewModel only handles 401. I've added an error state and checked it the same way.

An illustration of a session. The tool names are SimKit's own.

Why

An agent can read your code. It can't see your app run.

It doesn't know which request went out, what came back, or what happens on a 401 or a slow connection, so it guesses. SimKit already watches all of that beside your simulator. MCP hands it to the agent.

Tools

About 90 tools, grouped the way you work.

Your agent starts with the everyday ones and looks the others up as it needs them, so they don't fill its context.

Network

Read captured requests and WebSockets, export cURL and HAR, throttle the connection, generate Swift models and OpenAPI.

Mocks

Add and remove mocked responses, expire a token, play a bad-network scenario such as hotel Wi-Fi or a flapping connection.

Simulator

Boot, open links, set location and routes, appearance, text size, permissions, clipboard, Face ID and push notifications.

Apps and their data

Relaunch and reset apps; read and change UserDefaults, files, keychain, databases and cookies; save and restore an app's whole state.

Capture

Screenshots, video, the app's console, received pushes and links, an accessibility audit, and a zipped bug report.

Real devices

Many of the same tools on an iPhone or iPad that connects through the SimKit SDK or Xcode.

Setup

Three steps.

  1. Get SimKit

    The MCP server is part of the Mac app, from version 1.8. That version is in beta: on the home page, open the Download menu and choose Beta. SimKit 1.7 doesn't have it yet.

  2. Turn on Coding Agents

    Open SimKit's panel, go to the Agents tab and switch it on. It is off until you do.

  3. Connect your agent

    Add SimKit to your agent:

    Claude Code

    Terminal
    claude mcp add simkit -- npx -y simkit-mcp

    Cursor, Kiro and other clients

    mcp.json
    {
      "mcpServers": {
        "simkit": { "command": "npx", "args": ["-y", "simkit-mcp"] }
      }
    }

    Codex

    ~/.codex/config.toml
    [mcp_servers.simkit]
    command = "npx"
    args = ["-y", "simkit-mcp"]
Privacy

It stays on your Mac.

FAQ

Questions, answered.

Is it free?

Yes. SimKit and its MCP server are free, with no account.

Which coding agents does it work with?

Any MCP client. simkit-mcp works with any client that runs a command, including Claude Code, Cursor, Codex and Kiro.

Do I need the SimKit SDK?

For the simulator tools, no. Network capture, mocks and throttling need the one-line SimKit SDK in your debug build, or the DMG build of SimKit.

Can the agent tap and type in my app?

No. SimKit observes and sets things up: requests, mocks, app data, simulator settings and screenshots. Use it next to the tool you already build and tap with.

Does my app's data leave my Mac?

Not through SimKit. Headers and bodies reach your agent as the app sent them, tokens included, so treat them as you would any secret your agent can read. Tools that return them take a redact option.

It says SimKit isn't reachable.

Open SimKit and check that Coding Agents is on in the Agents tab. The agent connects to the app, so the app has to be running.

Give your agent eyes.

Free. MCP is in the 1.8 beta: choose Beta in the Download menu.