Signed-off-by: Matt Bruce <matt.bruce1@toyota.com>

docs/ai/ios/ios-mcp.md

@@ -20,11 +20,9 @@ There are two main ways to use MCP with iOS projects:
 - Best for seamless integration and live previews
 - [Setup & details](ios-xcodebuildmcp-xcode.md)
 
+
 ### 2. XcodeBuildMCP (External Tool)
-- Open-source bridge for Xcode used with other tools like VS Code.
+- For details and setup, see [XcodeBuildMCP for iOS in VS Code](ios-xcodebuildmcp-vscode.md).
-- More configuration and CI/CD options
-- Best for advanced automation or older Xcode setups
-- [Setup & details](ios-xcodebuildmcp-vscode.md)
 
 ## When to Use Which?
 - Use Xcode Native MCP for the simplest, most integrated experience (especially for new projects or live previews)

docs/ai/ios/ios-xcodebuildmcp-vscode.md

@@ -62,23 +62,6 @@ brew install xcodebuildmcp
 - The repo should include `.xcodebuildmcp/config.yaml`. Make sure it points to the correct workspace, scheme, and simulator.
 - [What is config.yaml? See reference and sample.](xcodebuildmcp-config.yaml.md)
 
-Example (Toyota):
-
-```yaml
-schemaVersion: 1
-sessionDefaults:
-	workspacePath: ./OneApp.xcworkspace
-	scheme: ToyotaOneApp
-	configuration: Debug
-	simulatorName: iPhone 17 Pro Max
-	simulatorId: <SIMULATOR_UDID>
-	useLatestOS: true
-```
-
-Notes:
-- Use either `simulatorName` or `simulatorId`. If both are set, `simulatorId` takes precedence.
-- The simulator must be installed and booted before running build/run.
-
 ### 3. Configure MCP in VS Code
 
 - Ensure `.vscode/mcp.json` exists: