Skip to main content
Glama

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). 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 npx setup 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

~/.cursor/mcp.json, or .cursor/mcp.json in a project

Claude Desktop

Settings › 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

Tool

What it does

Main parameters

list_targets

Running simulators and their apps, running Mac apps, presets and current rules

none

status

Every rule, what it's doing, and whether the proxy is running

none

set_network

Slow down or break one app's network

app, simulator; preset, or down/up (kbps), latency/jitter (ms), loss (%); failure (airplane, refuse, timeout, drop, outages); hosts, hosts_mode

reset_network

Back to full speed; the app stays watched

app, simulator

stop_watching

Turn the app's rule off entirely

app, simulator

relaunch_app

Relaunch a simulator app with request monitoring

app, simulator

get_requests

The app's recent HTTP requests, newest first

app, simulator, limit, filter (e.g. is:failed, status:5xx), include_bodies

fail_endpoint

Make one endpoint fail while the rest works

app, simulator, pattern, kind (offline, timeout, status, delay), value

mock_endpoint

Answer one endpoint with a made-up response

app, simulator, pattern, status, body, content_type, delay

clear_endpoints

Remove endpoint failures and mocks

app, 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.

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 tools
clear_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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control real iPhones and simulators on macOS, allowing for UI interaction, testing, and automation.
      90 npm
      98
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      10
      MIT