Lagsmith
Lagsmith MCP lets an AI agent control and inspect network conditions for one app at a time on macOS, including iOS Simulator apps.
List running simulators, installed apps, running Mac apps, presets, and active rules.
Show rule/proxy status.
Slow or break one app's network using presets or exact bandwidth, latency, jitter, and packet loss.
Simulate Airplane Mode, refused connections, timeouts, dropped connections, and repeating outages.
Limit rules to specific hosts or exclude hosts.
Reset an app to full speed while keeping it watched, or stop watching it entirely.
Relaunch a simulator app with request monitoring.
Read recent HTTP requests with status, timing, errors, filters, and optional bodies.
Make one endpoint fail via offline, timeout, HTTP status, or delay.
Mock one endpoint with a custom status, body, content type, and delay.
Clear all endpoint failures/mocks or those matching a pattern.
Throttles, breaks and mocks the network of individual iOS Simulator apps: applies 3G/Edge/LTE/Very Bad Network presets or exact bandwidth, latency, jitter and packet loss, forces Airplane Mode-like failures (refuse, timeout, drop, recurring outages), fails or mocks single endpoints, relaunches apps with request monitoring, and reads recent HTTP requests with status, timing and bodies.
Applies the same per-app network conditioning to individual Mac apps: throttling presets or custom bandwidth/latency/loss, host-scoped limits (only/except), failure modes, endpoint failure and mock rules, and request inspection, scoped to one app so the rest of the system stays at full speed.
Lagsmith MCP server
Let your AI coding agent test your app on bad networks. This MCP server lets Claude Code, Cursor, Codex, Claude Desktop, Windsurf and other MCP clients slow down, break and mock the network of one app at a time on your Mac, including iOS Simulator apps, using Lagsmith. Only the app under test is affected, so the agent's own connection, your terminal and your test runners stay at full speed.
With it, an agent can:
throttle one app to 3G, Edge, LTE or Very Bad Network, or set exact bandwidth, latency, jitter and packet loss
put one simulator app in Airplane Mode: requests fail with
NSURLErrorNotConnectedToInternet(-1009), andNWPathMonitorandSCNetworkReachabilityreport no network, like on a real devicerefuse, time out or drop connections, or take the app offline and back again on a loop
make one API endpoint fail or return a made-up response while the rest of the app works
read the app's recent HTTP requests with status, timing and bodies, to see what actually broke
Requirements
macOS 13 Ventura or later, on Apple silicon or Intel
Lagsmith in your Applications folder, running, with Allow Automation on (menu bar icon › Automation). Automation, including MCP, is part of Lagsmith Pro, and every install starts with a free 14-day Pro trial. See pricing.
Node.js 18 or later for the
npxsetup below, or skip Node and use the server inside the app
Related MCP server: iPhone MCP
Setup
Claude Code
claude mcp add --scope user lagsmith -- npx -y lagsmith-mcp--scope user makes Lagsmith available in every project. Start a new session and run /mcp to check it's connected.
Cursor, Claude Desktop, Windsurf and other JSON configs
{
"mcpServers": {
"lagsmith": {
"command": "npx",
"args": ["-y", "lagsmith-mcp"]
}
}
}Client | Config file |
Cursor |
|
Claude Desktop | Settings › Developer › Edit Config, then restart Claude Desktop |
Windsurf |
|
If the file already has other servers, add the lagsmith entry inside the existing mcpServers section.
Codex
In ~/.codex/config.toml:
[mcp_servers.lagsmith]
command = "npx"
args = ["-y", "lagsmith-mcp"]Without Node.js
The same server ships inside the app, so you can point any client straight at it:
claude mcp add --scope user lagsmith -- /Applications/Lagsmith.app/Contents/MacOS/lagsmith-mcpIn JSON configs, use "command": "/Applications/Lagsmith.app/Contents/MacOS/lagsmith-mcp" with no args.
Tools
Tool | What it does | Main parameters |
| Running simulators and their apps, running Mac apps, presets and current rules | none |
| Every rule, what it's doing, and whether the proxy is running | none |
| Slow down or break one app's network |
|
| Back to full speed; the app stays watched |
|
| Turn the app's rule off entirely |
|
| Relaunch a simulator app with request monitoring |
|
| The app's recent HTTP requests, newest first |
|
| Make one endpoint fail while the rest works |
|
| Answer one endpoint with a made-up response |
|
| Remove endpoint failures and mocks |
|
For simulator apps, pass simulator: "booted", a device name or a UDID. Leave simulator out for a Mac app.
Example prompts
"Relaunch the app on 3G with monitoring, sign in, and list requests slower than two seconds."
"Put the app in Airplane Mode and check that the offline banner appears."
"Make POST /v1/orders return 500 and check the app shows a retry button."
"Run the checkout UI tests on 3G with the payments API returning 503s, and tell me what breaks."
See a full example session in the MCP docs.
How it works
lagsmith-mcp speaks MCP over stdio and turns each tool call into a request to Lagsmith's automation server on 127.0.0.1:47300 (set LAGSMITH_PORT to change the port). It's one dependency-free Swift file: Sources/lagsmith-mcp.swift, the same source that's built into the app.
The npm package is a small launcher. It runs the server inside your installed copy of Lagsmith, so the server always matches your app version. If Lagsmith isn't installed, the launcher still answers with the list of tools, and every tool call explains how to install the app. If your copy of Lagsmith isn't in /Applications or ~/Applications, set LAGSMITH_APP to its path.
To build the server yourself:
xcrun swiftc -O -o lagsmith-mcp Sources/lagsmith-mcp.swiftPrivacy
Everything runs on your Mac. The requests Lagsmith slows down, mocks or shows you are never sent anywhere. Lagsmith's anonymous usage statistics count which features are used, including tool calls through MCP. They never include your apps' traffic. See the privacy policy. What your AI agent does with what it reads is governed by that agent's own privacy policy.
Links
License
This repository, the MCP server and its npm launcher, is under the MIT License. The Lagsmith app itself is proprietary: see the terms.
Available Tools
10 toolsclear_endpointsB
Remove an app's endpoint failures and mocks: all of them, or those for one pattern.
Inputs: app (required), pattern, simulator.
fail_endpointA
Make requests to one endpoint fail inside a simulator app while the rest of the app works.
Inputs: app (required), kind (required), pattern (required), simulator (required), +1 more.
get_requestsA
A simulator app's recent HTTP requests, newest first: method, URL, status, errors, time, and optionally bodies. Needs the app to have been launched with request monitoring (relaunch_app).
Inputs: app (required), simulator (required), limit, filter, +1 more.
list_targetsB
List running simulators and the apps installed on them, running Mac apps, the presets, and the current rules.
Inputs: no named parameters.
mock_endpointB
Answer requests to one endpoint in a simulator app with a made-up response, without reaching the server.
Inputs: app (required), pattern (required), simulator (required), body, +3 more.
relaunch_appA
Quit and reopen a simulator app with request monitoring, so every connection it makes goes through its rule and its requests are recorded. Do this after the first set_network for an app that was already running.
Inputs: app (required), simulator (required).
reset_networkA
Put an app back to full speed with no failures, host limits or endpoint rules. It stays watched, so its requests still show.
Inputs: app (required), simulator.
set_networkA
Slow down or break one app's network, and only that app's. Creates the rule if needed and turns it on. Combine a preset with exact values or a failure mode.
Inputs: app (required), up, down, loss, +11 more.
statusB
Show every rule, what it's doing, and whether Lagsmith's proxy is running.
Inputs: no named parameters.
stop_watchingA
Turn off an app's rule. Its traffic goes back to normal and stops being watched.
Inputs: app (required), simulator.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have clearly distinct scopes: whole-app network shaping, endpoint-specific failure/mocking, request inspection, and lifecycle controls. The main overlap is between list_targets and status, since both expose current rules; reset_network, stop_watching, and clear_endpoints are also related but descriptions distinguish them.
The set mostly follows a snake_case verb_noun convention such as set_network, fail_endpoint, and clear_endpoints. The only notable deviation is the bare noun status, which breaks the pattern slightly but remains clear.
Ten tools is well scoped for an app network-conditioning and request-inspection server. Each tool supports a distinct step in the workflow: discovery, rule lifecycle, endpoint behavior, relaunching, and request review.
The surface covers the core lifecycle: discovering targets, applying/resetting/stopping network rules, failing or mocking endpoints, clearing endpoint rules, relaunching for monitoring, and fetching requests. Minor gaps exist around bulk rule management and explicit host-limit/preset editing, but the main workflows are covered.
Maintenance
Related MCP Connectors
Cloud iPhone Simulators for AI agents: build the Xcode project, read the screen, tap by label, test.
Cloud iPhones and Macs with Xcode for AI agents: build, run and test iOS apps, use the screen.
Let your AI agent control real iPhones: screenshots, tap, swipe, type and open apps.
The cloud Mac alone, with Xcode, for AI agents: run commands, build and test, use the screen.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI to control iOS simulators through the MCP protocol. Supports device management, UI automation, and network interception including screenshot capture, text input, and HTTP request mocking.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control real iPhones and simulators on macOS, allowing for UI interaction, testing, and automation.90 npm98MIT
- AlicenseNot gradedqualityDmaintenanceGives AI agents the ability to interact with iOS simulators through 21+ tools for mobile app testing.10,447 npmMIT
- 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