iOS Agent Skill
Give your coding agent the Apple references, Swift source and local tools it needs to build and review an iOS app.
Watch the website walkthrough · Explore the website
Use it to turn an app idea into an editable starter, improve an existing Swift project, and check the result with Xcode and the simulator. Your agent writes the app; this repository supplies reusable implementation guidance and tools to inspect its work.
Explore the website · Client setup guides · npm · Release notes
Start with one connection
For Claude Code:
claude mcp add ios-agent -- npx -y ios-agent-mcp@latest
Set up ChatGPT/Codex, Gemini CLI or Muse. One npm package includes reviews, local references, app scaffolding and simulator tools. Node.js 20+ is required; building and running iOS apps needs macOS and Xcode.
Then ask:
Build a SwiftUI reading list with local persistence, search and accessible empty/error states. Reuse the local source library. Build it, run the tests and capture simulator evidence. Explain any checks that fail.
For an existing app, provide its absolute project path and ask for a focused review before making changes.
What it helps you do
| Feature | What you get |
|---|
| Start an app | An editable Swift starter, implementation brief and optional XcodeGen specification. |
| Reuse Apple knowledge | Search local Swift source and guides in bounded sections, plus a dated directory of Apple technologies and release notes. |
| Review Swift code | File-located findings for concurrency, architecture, SwiftUI, availability, security, performance and App Intents. |
| Generate design assets | Named light/dark/high-contrast colors and an opaque 1024px app icon rendered locally from editable SVG layers. |
| Review app color systems | Generate semantic palettes and inspect light, dark and high-contrast color evidence. |
| Review backend integration | Identify supported services and review credential, auth, policy and networking evidence locally. |
| Verify on a simulator | Build, test, install, launch and capture screenshots through Xcode. |
| Review launch screens | Conservative target-aware checks for launch configuration, storyboards and asset references. |
| Prepare a local release draft | Inspect selected-target facts, unresolved questions and hashed, resumable local packages without connecting to Apple. |
Asset generation · Review tools · Simulator setup · Apple release status
Create a starter directly:
npx -y ios-agent-mcp@latest new MyApp --brief "A reading list with local storage" --xcodegen
XcodeGen is needed to generate the Xcode project. The starter is not a finished app. Generated app ownership and branding belong to the user.
See the evidence
The Reading List demo has persistence, search, simulator acceptance tests and captured screens.
The 2.7.2 server exposes 40 tools. Static reviews are heuristics, not compiler diagnostics. The Apple directory is a reference map, not Apple's proprietary framework source or proof of 405 working integrations. Token savings have not been benchmarked. Build-loop verification limits.
Why use this alongside Xcode?
Xcode already ships agent expertise and build/test tools. Use those when they meet your needs. This repository adds shared guidance across these four client families, inspectable review rules, local source retrieval and repeatable asset workflows. It has not been established that it makes an AI outperform Xcode's skills or use fewer tokens.
Where the guidance comes from, evidence and unfinished work. The paired benchmark harness contains 20 Swift microtasks; results are not published, and it does not yet measure complete app builds.
Failure feedback belongs in your coding session: the observed error, the proposed fix and actual verification results. The source server adds troubleshooting guidance to returned tool errors; agent instructions also cover compiler/test failures. These messages do not appear in the app you are building.
prepare_issue_report lets your AI prepare a local report when an iOS Agent tool fails. It accepts fixed categories only, shows a preview and a duplicate-search link, and leaves public submission to you. No app source or logs are collected. Reporting workflow.
Included as an experimental tool in 2.7.1: optional private_feedback keeps approval in the AI chat and sends fixed categories to a private inbox through a configured HTTPS receiver. Hosting is not configured, so private submission is not live. It never silently submits or falls back to public issues.
Four client families, one project
| Client | Setup and evidence |
|---|
| Claude | Local MCP and source skill; your Claude client supplies the coding agent. |
| ChatGPT / Codex | Codex local MCP; ChatGPT skills package or a separately configured HTTPS/private-tunnel MCP connection. Availability depends on account/workspace policy. |
| Gemini CLI | Extension configuration and local MCP connection verified. |
| Muse Code | Skill discovery, 36-tool MCP discovery and a Stop hook verified; model sessions and observer behavior remain unverified. |
The project focuses on these four families. For another client, open a client-support request or add a 👍 to an existing request. Votes inform priorities alongside feasibility and testing; they do not guarantee delivery. Existing experimental adapters are not actively maintained.
install.sh is optional: it installs source guidance for a chosen local client, not the MCP server or a browser plugin. Run bash install.sh --help after cloning. Most users should use the client setup guide above.
Reference coverage
Apple catalog tracked: 99 technologies. Covered: 99. Planned: 0. Skipped: 0. Deprecated: 0. Coverage: 100.0%.
Source of truth: frameworks.json. Human index: docs/apple-framework-index.md.
Coverage counts describe documentation, not compiled integrations. Download counts refresh daily and are not unique users.
Contributing · Development · Security · Roadmap · MIT license
https://www.producthunt.com/products/ios-agent-mcp?launch=ios-agent-mcp
Backend integration guidance: choose a service and review auth, data and security boundaries.
