Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Swift reviews, local Apple references, app scaffolding and iOS simulator workflows.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"ios-agent-skill": {
"command": "npx",
"args": [
"-y",
"ios-agent-mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add ios-agent-skill -- npx -y ios-agent-mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ios-agent-skill": {
"command": "npx",
"args": [
"-y",
"ios-agent-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ios-agent-skill": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ios-agent-mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub Nagarjuna2997, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.6.0) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Systemdox
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Describe an app in one sentence and the /ios-build agent plans it, writes the SwiftUI code and Xcode project, then builds and runs it in the simulator (what has been verified, example apps on the website). For an existing project, the same package gives your coding agent reviews, local Apple references and simulator tools to check its work.
Explore the website · Client setup guides · npm · Release notes
/ios-build " " asks Claude Code to plan an iOS app, write its SwiftUI code and Xcode project, apply capability modules (sign-in, storage, payments, maps and more), then build, run and screenshot it in the iOS Simulator, ending with a report of what needs your accounts or money. Published tools are in ios-agent-mcp 2.10.2 (npm verified October 15, 2026), including plan-driven design tokens, sample data, palette-aligned assets, light/dark/XXL screenshot evidence, deployment-target checks and App Store readiness reports. Four existing apps built and ran on Xcode 27.0; see examples/agent for refreshed evidence.
Install the published server and Claude Code command:
claude mcp add ios-agent -- npx -y ios-agent-mcp@latest
npx -y ios-agent-mcp@latest install-command --global
Then, in any Claude Code session on a Mac with Xcode 16 or later:
/ios-build "A habit tracker with a list, a detail screen, and settings with dark mode toggle"
Shipping (unreleased GitHub source): ios-agent-mcp ship prepares screenshot sets and metadata, then offers separately approved signing/archive and TestFlight upload steps. Setup and limitations. Live signed distribution is not yet verified; npm is unchanged.
Windows/Linux or cloud client: the GitHub source now includes build --remote for unsigned builds and simulator screenshots on GitHub Actions. It requires a destination repository, GitHub CLI authentication and pinned toolkit/Xcode versions. See remote macOS setup and billing. npm publication is deferred.
XcodeGen is optional: without it, the agent writes a folder-synchronized Xcode project itself. The steps are described in docs/tooling/ios-build-agent.md. The four screenshot examples reused existing app folders; this exact one-sentence quickstart has not yet been run from planning through code generation in one Mac session.
| Habit tracker | Notes with search | Three-tab feed | Food delivery |
|---|---|---|---|
Plans, generated sources, run reports and what was and was not exercised: examples/agent.
Every capability is a folder in capabilities/ with a manifest, recipe, Swift template, apply hook and verify hook. The catalog lists the wider landscape for planning and cost estimates. The counts below are generated from the manifests.
| Status | Capabilities |
|---|---|
| Verified on a Mac | 7 |
| Module exists, not yet verified on a Mac | 41 |
| ...of which the Swift compiled on a Mac (combined compile check) | 41 |
| Blocked | 0 |
| Listed for planning only | 114 |
162 catalog entries in 31 categories; generated from capabilities/CATALOG.md.
The agent builds and runs everything in the simulator without accounts. Capabilities that need a service declare the keys in their manifest. Client keys, such as a publishable key, go in the project's gitignored .env file and reach the app through a generated xcconfig. Until they are set, the keys are REPLACE_ME placeholders, so the app still builds and shows a configuration message. Server secrets are never put in the app. PLAN.md lists what each run needs and the cost model of each service. Running on a device, using TestFlight or publishing needs your Apple Developer Program membership.
| You want to | Use | Notes |
|---|---|---|
| Build a new app from a description | /ios-build " " in Claude Code, or ios-agent-mcp build | Plans, writes, builds, runs and screenshots; see above. Available in npm 2.10.2 and GitHub main. |
| Make an existing project pass your own acceptance tests | ios-agent-mcp loop | Runs the checks you write and asks Claude to repair failures; see the app-building loop and the Reading List demo. |
| Get an editable starter only | ios-agent-mcp new MyApp | A starting point with a brief, not a finished app. |
| Review or extend code you already have | The MCP tools below | File-located reviews, local references, assets and simulator checks. |
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; local iOS builds need macOS and Xcode; the GitHub-source remote lane runs those steps on Actions.
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.
| Feature | What you get |
|---|---|
| Build an app from a sentence | The ios-build agent plans screens, data and capabilities, writes SwiftUI and the Xcode project, then builds, runs and screenshots the app in the simulator. Available in ios-agent-mcp 2.10.0. |
| 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. |
| App Store Screenshot Studio (GitHub source) | Turn captures into localized screenshot sets with reusable layouts, neutral frames, a preview gallery and validated PNG exports. |
| Apple system integrations (GitHub source) | Preview and review Calendar, Reminders, Contacts, Photos, Camera, Maps, Files, Sharing, Shortcuts and Notifications with permission and capability evidence. |
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
The starter is not a finished app: --xcodegen writes a project.yml that XcodeGen turns into a project. For a complete app from a description, use /ios-build. Generated app ownership and branding belong to the user.
The Reading List demo has persistence, search, simulator acceptance tests and captured screens. The four apps the /ios-build agent planned and wrote, with their plans, run reports and simulator screenshots, are in examples/agent.
The published npm 2.10.2 package includes the build-agent tools, deployment-target checks and App Store readiness reports. They include seven Apple system integration tools and nine Screenshot Studio 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.
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 rev
Solo se muestra el principio; lee el resto en el repo