Lagsmith MCP

Let AI coding agents test your app on bad networks. Slow down, break or mock the network of one app at a time on a Mac, including iOS Simulator apps: 3G/Edge/LTE presets, Airplane Mode, time-outs, failing or mocked endpoints, and reading the app's requests. The agent's own connection stays at full speed. Requires Lagsmith (lagsmith.com).

文档

Lagsmith

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), and NWPathMonitor and SCNetworkReachability report no network, like on a real device
  • refuse, 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). Lagsmith is free during the beta.
  • Node.js 18 or later for the npx setup below, or skip Node and use the server inside the app

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"]
    }
  }
}
ClientConfig file
Cursor~/.cursor/mcp.json, or .cursor/mcp.json in a project
Claude DesktopSettings › Developer › Edit Config, then restart Claude Desktop
Windsurf~/.codeium/windsurf/mcp_config.json

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-mcp

In JSON configs, use "command": "/Applications/Lagsmith.app/Contents/MacOS/lagsmith-mcp" with no args.

Tools

ToolWhat it doesMain parameters
list_targetsRunning simulators and their apps, running Mac apps, presets and current rulesnone
statusEvery rule, what it's doing, and whether the proxy is runningnone
set_networkSlow down or break one app's networkapp, simulator; preset, or down/up (kbps), latency/jitter (ms), loss (%); failure (airplane, refuse, timeout, drop, outages); hosts, hosts_mode
reset_networkBack to full speed; the app stays watchedapp, simulator
stop_watchingTurn the app's rule off entirelyapp, simulator
relaunch_appRelaunch a simulator app with request monitoringapp, simulator
get_requestsThe app's recent HTTP requests, newest firstapp, simulator, limit, filter (e.g. is:failed, status:5xx), include_bodies
fail_endpointMake one endpoint fail while the rest worksapp, simulator, pattern, kind (offline, timeout, status, delay), value
mock_endpointAnswer one endpoint with a made-up responseapp, simulator, pattern, status, body, content_type, delay
clear_endpointsRemove endpoint failures and mocksapp, simulator, pattern

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.swift

Privacy

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.