ios-agent-mcp 2.5.0 → 2.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,9 +1,9 @@
1
1
  # iOS Agent MCP
2
2
 
3
- ## One install, one MCP connection (2.5.0)
3
+ ## One install, one MCP connection (2.5.1)
4
4
 
5
5
  ```bash
6
- claude mcp add ios-agent -- npx -y ios-agent-mcp@2.5.0
6
+ claude mcp add ios-agent -- npx -y ios-agent-mcp@2.5.1
7
7
  ```
8
8
 
9
9
  The default server exposes 34 tools: 11 Swift reviews, 8 Apple reference tools, 14 simulator tools, and `create_app`. App scaffolding and simulator packages install automatically as dependencies; no separate installation or MCP connection is needed. Remove the separate knowledge/simulator connections if you previously configured them to avoid duplicate tools.
@@ -11,7 +11,7 @@ The default server exposes 34 tools: 11 Swift reviews, 8 Apple reference tools,
11
11
  Create a starter directly:
12
12
 
13
13
  ```bash
14
- npx -y ios-agent-mcp@2.5.0 new MyApp --brief "A reading list with local storage" --xcodegen
14
+ npx -y ios-agent-mcp@2.5.1 new MyApp --brief "A reading list with local storage" --xcodegen
15
15
  ```
16
16
 
17
17
  Requires Node.js 20+. Simulator operations require macOS and Xcode; XcodeGen is required to generate an Xcode project from the starter specification. The agent implements app features using the starter, source tools and verification tools. One install is not autonomous app generation. The default connection now includes tools that write files and operate the simulator; review and reference tools remain read-only.
@@ -162,18 +162,13 @@ The root comes from `--project`, then `IOS_AGENT_PROJECT`, then the working
162
162
  directory the client spawned the server in. **Every payload reports which root it
163
163
  used**, so an empty project is never mistaken for a wrong path.
164
164
 
165
- **There is deliberately no `ios://project/build-status`.** It would have to run
166
- `xcodebuild`, which needs macOS and Xcode and breaks the
167
- `filesystem: read, network: none` contract that lets this package install
168
- anywhere in ~26 KB. Build and simulator state belong in the separate package that
169
- already requires a full toolchain — see [ROADMAP.md](../ROADMAP.md).
165
+ Project resources remain read-only snapshots. Build, test and simulator actions are available as tools in the unified connection; they require macOS/Xcode.
170
166
 
171
167
  ---
172
168
 
173
169
  ## What it does and does not do
174
170
 
175
- **Does:** static analysis. Reads `.swift`, `Info.plist`, `Package.swift`, and
176
- `project.pbxproj` under the path you give it. No network, no writes.
171
+ **Review tools:** read project files without modifying them. **App creation:** writes a new starter. **Simulator tools:** build/test projects and operate devices; builds can fetch dependencies, and preview starts a loopback server.
177
172
 
178
173
  **Does not:** prove your app builds or behaves correctly. Run `swift build` and
179
174
  `swift test` for that — the tools say so in their own output.