SimKit MCP
Provides tools to inspect and control iOS apps running in the Simulator, including network requests and mocks, simulator actions, app data, screenshots, video, logs, and bug reports.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
SimKit MCP
Let Claude Code, Cursor, Codex and other coding agents see what your iOS app actually does: the requests it sends, the responses it gets, and how it behaves when the server returns a 500 or the network is slow. The agent can also drive the simulator: relaunch, screenshot, dark mode, location, push, deep links, app data.
This package is a small bridge. The tools themselves live in SimKit for Mac, which is free; the bridge connects your agent to the SimKit app running on the same Mac.
Beta. This needs SimKit 1.8, which is in beta: pick Beta from the Download menu on simkit.dev. SimKit 1.7 has no MCP server.
Requirements
macOS with SimKit 1.8 beta or later, running, with Coding Agents turned on in the Agents tab
Node.js 18 or later
Related MCP server: ios-simulator-bridge
Install
Claude Code
claude mcp add simkit -- npx -y simkit-mcpOr as a plugin, which also adds a skill that teaches the agent when to use SimKit:
claude plugin marketplace add ealtaca/simkit-mcp
claude plugin install simkit@simkitCursor, Kiro and other clients — add to the client's MCP config:
{
"mcpServers": {
"simkit": { "command": "npx", "args": ["-y", "simkit-mcp"] }
}
}Codex — in ~/.codex/config.toml:
[mcp_servers.simkit]
command = "npx"
args = ["-y", "simkit-mcp"]If you already pressed Install in SimKit's Agents tab, your client is connected over HTTP and you don't need this package as well.
Try it
"List the requests my app made in the last minute and tell me which ones failed."
"Mock /login to return a 500, relaunch the app and take a screenshot."
"Throttle the network to 3G and tell me which requests get slow."
"Create a bug report for my app."
What agents can do
Area | Examples |
Network | list and inspect requests and WebSockets, export cURL/HAR, throttle, generate models and OpenAPI |
Mocks | add and remove mocked responses, expire a token, run a network scenario |
Simulator | boot, open links, location, appearance, text size, permissions, clipboard, Face ID, push |
Apps and data | relaunch, reset, UserDefaults, files, keychain, databases, cookies, whole-state snapshots |
Capture | screenshots, video, console logs, bug report bundle |
SimKit has about 90 tools. To keep your agent's context small, the bridge lists some 20 of them and the agent looks the others up as it needs them. Tools that only read are run through read_tool, which is marked read-only, so a client that asks before every change doesn't ask before a lookup.
Network capture needs either the SimKit SDK in your app or the direct-download build of SimKit.
How it works, and what it touches
SimKit serves MCP on 127.0.0.1 only, protected by a token. This bridge is one dependency-free Node script (server/simkit-mcp.mjs). Everything it does:
Reads one value from your Mac: SimKit's agent token, from SimKit's own settings file (
~/Library/Containers/com.simkit.app/Data/Library/Preferences/com.simkit.app.plist), using/usr/bin/plutil. It reads nothing else.Talks to one address:
http://127.0.0.1:47290/mcp, the SimKit app on the same Mac. It sends the token there and nowhere else, and makes no other network request.Writes nothing to disk, and collects no analytics.
What the tools return (requests, headers, bodies, screenshots) comes from the SimKit app and goes to your agent, which sends it to its model provider like anything else it reads. SimKit's own data handling is in its privacy policy.
Variable | Use |
| Use this token instead of reading SimKit's settings |
| SimKit's MCP port, if you changed it (default 47290) |
|
|
| Read the token from another SimKit build's settings |
Troubleshooting
"SimKit isn't reachable" — open SimKit and turn on Coding Agents in the Agents tab.
"SimKit refused the token" — set
SIMKIT_MCP_TOKENto the token shown in the Agents tab.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.
Cloud iOS simulators and Android emulators your agent can create, drive, and throw away.
Capture, inspect & debug HTTPS traffic across iOS, Android, browsers & backends — 304 MCP tools.
Let your AI agent control real iPhones: screenshots, tap, swipe, type and open apps.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate a real iPhone from a Mac by reading the screen over USB and sending taps, swipes, typing, and app launches over Bluetooth, with every action returning a fresh screenshot so the agent can verify its work. Runs as a local MCP server, so agents can test iOS apps on physical devices and automate everyday phone tasks.38 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to check setup, manage iOS Simulator devices, build/install/launch iOS apps, capture screenshots, send input, and open a live browser preview. It connects local agent workflows to Apple's simulator without requiring a custom emulator or native pane.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and control connected iPhones, iPads, and iOS simulators through local Mac tools, including device previews, UI and OCR inspection, builds, and session-bound approvals.1GPL 3.0
- AlicenseAqualityCmaintenanceEnables agent-driven service-level capture and review of iPhone app traffic on Windows by coordinating a hotspot, passive packet capture, and an HTTPS interception proxy, with records and reports stored in SQLite.131MIT