MCP server de iOS WebKit Debug Proxy
Commit 3 oct 2026Permite que un cliente de IA depure Safari en dispositivos iOS reales, ejecutando JavaScript, inspeccionando el DOM/CSS, interceptando la red y realizando perfiles de rendimiento.
También conocido como nnemirovsky/iwdp-mcp
- Stars
- 21
- Herramientas
- 10
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 3 oct 2026
- Licencia
- MIT
¿Qué es iOS WebKit Debug Proxy MCP?
Permite que un cliente de IA depure Safari en dispositivos iOS reales, ejecutando JavaScript, inspeccionando el DOM/CSS, interceptando la red y realizando perfiles de rendimiento. Expone 10 herramientas, como iwdp_status, restart_iwdp, list_devices.
Resumen generado a partir del README del proyecto
Acerca del MCP server de iOS WebKit Debug Proxy
Los desarrolladores web y los ingenieros de QA pueden depurar Safari en dispositivos iOS físicos directamente a través de un agente de IA. Este servidor cierra la brecha entre los asistentes de IA y WebKit al proporcionar acceso a más de 100 herramientas en 27 dominios de protocolo. Permite una inspección profunda de entornos web móviles a los que las herramientas de depuración estándar de escritorio no pueden llegar, como el acceso a cookies httpOnly que son invisibles para el JavaScript estándar.
Para usar este servidor, debes conectar un dispositivo iOS mediante USB y tener instalado ios-webkit-debug-proxy en tu máquina. El servidor funciona con varios clientes compatibles con MCP, incluyendo Claude Code, VS Code, Cursor, Windsurf y los IDE de JetBrains. Permite realizar tareas complejas como inspeccionar el DOM, gestionar estilos CSS, interceptar solicitudes de red y realizar perfiles de rendimiento mediante comandos como evaluate_script, take_screenshot y heap_snapshot.
Qué puedes hacer con él
- 1Inspeccionar el DOM y estilos móvilesPide a la IA que encuentre elementos específicos o verifique reglas de CSS computadas en una pestaña activa de Safari en un iPhone.
- 2Depurar la red y las cookiesHaz que el agente monitoree llamadas a la API o recupere cookies seguras que de otro modo serían inaccesibles.
- 3Realizar perfiles de rendimientoInstruye a la IA para capturar instantáneas de memoria o perfiles de CPU para identificar cuellos de botella en el rendimiento móvil.
- 4Automatizar la ejecución de JavaScriptUsa el agente para ejecutar scripts o establecer puntos de interrupción dentro del entorno del navegador móvil.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Herramientas de iOS WebKit Debug Proxy MCP 10
Detectado desde el READMEiwdp_statusrestart_iwdplist_deviceslist_pagesselect_pagenavigatetake_screenshotevaluate_scriptget_documentquery_selector
| iwdp_status | — | |
| restart_iwdp | — | |
| list_devices | — | |
| list_pages | — | |
| select_page | — | |
| navigate | — | |
| take_screenshot | — | |
| evaluate_script | — | |
| get_document | — | |
| query_selector | — |
Configuración
IWDP_SIM_WS_URL
| Nombre | Descripción | Tipo |
|---|---|---|
| IWDP_SIM_WS_URL | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblennemirovsky/iwdp-mcp is public and reachablegithub.com/nnemirovsky/iwdp-mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-03github.com/nnemirovsky/iwdp-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubiOS WebKit Debug Proxy MCP Server + CLI
Debug iOS Safari from your AI agent. No existing tool lets AI assistants interact with Safari on a real iPhone. Chrome DevTools MCP speaks CDP, which is incompatible with WebKit. This project bridges that gap.
100+ tools across all 27 WebKit Inspector Protocol domains — navigation, screenshots, DOM inspection, CSS, network interception, httpOnly cookies, JS debugging, heap snapshots, profiling, and more. Full feature parity between MCP server and CLI.
Why?
- Chrome DevTools MCP exists for desktop Chrome. Nothing existed for iOS Safari — until now.
- httpOnly cookies are invisible to
document.cookie. This tool reads them via the protocol. - Real device testing catches iOS-specific bugs that simulators miss.
- Works with Claude Code, VS Code, Cursor, Windsurf, Codex CLI, Antigravity, JetBrains, and any MCP-compatible client.
Installation
Prerequisites
# Install ios-webkit-debug-proxy (macOS)
brew install ios-webkit-debug-proxy
# Connect an iOS device via USB and enable Web Inspector:
# Settings → Safari → Advanced → Web Inspector → ON
For Linux and other platforms, see the ios-webkit-debug-proxy installation guide.
Claude Code Plugin (recommended)
Inside Claude Code, run:
/plugin marketplace add nnemirovsky/iwdp-mcp
/plugin install iwdp-mcp
Go Install
go install github.com/nnemirovsky/iwdp-mcp/cmd/...@latest
Pre-built Binaries
Download from GitHub Releases.
Build from Source
git clone https://github.com/nnemirovsky/iwdp-mcp.git
cd iwdp-mcp
make build
Quick Start
CLI
# Start the proxy
ios_webkit_debug_proxy --no-frontend &
# List connected devices (port 9221)
iwdp-cli devices
# List Safari tabs on the first device (port 9222)
iwdp-cli pages
# Evaluate JavaScript
iwdp-cli eval "document.title"
# Take a screenshot
iwdp-cli screenshot -o page.png
# Show all cookies (including httpOnly)
iwdp-cli cookies
MCP Server
Install as a plugin (recommended):
/plugin marketplace add nnemirovsky/iwdp-mcp
/plugin install iwdp-mcp
Or add to your project's .mcp.json:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Or via CLI:
claude mcp add iwdp-mcp -- iwdp-mcp
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Click the install badges at the top of this README, or add to .vscode/mcp.json:
{
"servers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Or via CLI:
code --add-mcp '{"name":"iwdp-mcp","command":"iwdp-mcp"}'
Click the Cursor install badge at the top of this README, or add to .cursor/mcp.json:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
codex mcp add iwdp-mcp -- iwdp-mcp
Or add to ~/.codex/config.toml:
[mcp_servers.iwdp-mcp]
command = "iwdp-mcp"
Add to ~/.gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add, or add the following JSON config:
{
"mcpServers": {
"iwdp-mcp": {
"command": "iwdp-mcp"
}
}
}
Example Prompts
Once the MCP server is configured, you can ask your AI assistant things like:
Getting started
Connect to my iPhone's Safari and show me what tabs are open
Take a screenshot of the current page
What's the page title and URL?
JavaScript & DOM
Run document.querySelectorAll('a') and list all links on the page
Find all elements with class "error" and show their text content
Get the full DOM tree of the page
What event listeners are attached to the submit button?
Highlight the navigation bar so I can see its bounds
CSS & Styles
What CSS rules are applied to the header element?
Show me the computed styles for the main content area
Force the :hover state on the dropdown menu
Change the background color of .hero to #f0f0f0
List all stylesheets loaded on this page
Network
Monitor network requests while I interact with the page
Show me the response body of that failed API call
Intercept all requests to api.example.com and log them
Block all requests to analytics.google.com
Set a custom Authorization header for all requests
Throttle the network to simulate a slow 3G connection
Disable the browser cache and reload the page
Storage & Cookies
Show me all cookies including httpOnly and secure ones
Set a session cookie named "debug" with value "true"
Delete the authentication cookie
What's in localStorage for this site?
Set a localStorage item "theme" to "dark"
List all IndexedDB databases and their object stores
Show me the data in the "users" object store
Debugging
Set a breakpoint in main.js at line 42
Pause execution and show me the call stack
Step through the code and show variable values
What's the source of the script at bundle.js?
Search for "addEventListener" across all loaded scripts
Break on any uncaught exceptions
Set a DOM breakpoint — break when the #content div is modified
Performance & Profiling
Start a timeline recording while I navigate through the app
Take a heap snapshot and find potential memory leaks
Profile the CPU usage while this animation runs
Track memory usage while I scroll through the feed
Force a garbage collection
Advanced
List all compositing layers and why they were composited
Show me all active CSS animations on the page
Capture the canvas content as an image
Get the TLS certificate details for this page
Check if there are any web workers running
How It Works
┌────────────┐ USB ┌──────────┐ HTTP/WS ┌──────────┐
│ iOS Device │◄──────────►│ iwdp │◄────────────►│ iwdp-mcp │
│ (Safari) │ │ :9221-N │ │ or CLI │
└────────────┘ └──────────┘ └──────────┘
ios-webkit-debug-proxy exposes:
- Port 9221 — lists all connected devices
- Port 9222+ — each device gets an incremented port listing its Safari tabs
- Each tab provides a WebSocket URL for the WebKit Inspector Protocol
iwdp-mcp connects to those WebSocket endpoints and exposes 100+ tools.
Tools
Core
| Tool | Description |
|---|---|
iwdp_status |
Check/auto-start ios-webkit-debug-proxy |
restart_iwdp |
Restart iwdp after a crash (e.g., heap snapshot) |
list_devices |
List connected iOS devices (HTTP GET :9221) |
list_pages |
List Safari tabs (HTTP GET :9222+) |
select_page |
Connect to a specific tab |
navigate |
Go to URL |
take_screenshot |
Capture page as PNG |
evaluate_script |
Run JavaScript |
get_document |
Get DOM tree |
query_selector |
Find elements by CSS selector |
DOM & CSS
get_outer_html, get_attributes, get_event_listeners, highlight_node, get_matched_styles, get_computed_style, set_style_text, force_pseudo_state, and more.
Network
network_enable, list_network_requests, get_response_body, set_request_interception, intercept_continue, intercept_with_response, set_emulated_conditions, set_resource_caching_disabled.
Storage
get_cookies (httpOnly + secure), set_cookie, delete_cookie, get_local_storage, get_session_storage, list_indexed_databases, get_indexed_db_data.
Debugging
debugger_enable, set_breakpoint, pause, resume, step_over, step_into, step_out, get_script_source, evaluate_on_call_frame, set_pause_on_exceptions.
Performance
timeline_start/stop, memory_start/stop_tracking, heap_snapshot, cpu_start/stop_profiling, script_start/stop_profiling.
More
Animation, Canvas, LayerTree, Workers, Audit, Security (TLS certificates), and element interaction (click, fill, type_text).
Development
make build # Build both binaries
make test # Run unit + smoke tests
make test-e2e # E2E tests (boots iOS Simulator, tests all tools)
make test-coverage # Tests with coverage report
make lint # golangci-lint
make fmt # gofumpt formatting
Testing
Unit tests use a mock WebSocket server (internal/webkit/testutil/) that simulates the WebKit Inspector Protocol. E2E tests boot an iOS Simulator and run every tool against real Safari.
# Unit + smoke tests (no device needed)
make test
# E2E tests — boots iOS Simulator + iwdp, tests ALL tools against real Safari
make test-e2e
# Or manually for debugging:
make sim-setup # Prints IWDP_SIM_WS_URL
export IWDP_SIM_WS_URL=ws://localhost:9222/devtools/page/1
go test -tags=simulator ./e2e/ -v -run TestSim_Navigate
make sim-teardown
Note: E2E tests require macOS with Xcode and
ios-webkit-debug-proxyinstalled. GitHub Actionsmacos-latestrunners have Xcode and iOS Simulator runtimes pre-installed.
Project Structure
iwdp-mcp/
├── cmd/
│ ├── iwdp-mcp/ # MCP server (stdio transport)
│ └── iwdp-cli/ # CLI tool
├── internal/
│ ├── webkit/ # WebKit Inspector Protocol client
│ │ ├── client.go # WebSocket connection + message routing
│ │ ├── types.go # Protocol type definitions
│ │ ├── domains.go # Domain enable/disable helpers
│ │ └── testutil/ # Mock WebSocket server
│ ├── tools/ # Tool implementations (shared by both binaries)
│ └── proxy/ # iwdp process detection + management
├── skills/ # Claude Code skill definition
├── .claude-plugin/ # Claude Code plugin manifest
└── .mcp.json # MCP server configuration
License
MIT — see LICENSE.
ios-webkit-debug-proxy is a separate project licensed under BSD-3-Clause. This tool connects to it over HTTP/WebSocket at runtime without bundling its code.
Preguntas sobre iOS WebKit Debug Proxy MCP
¿Qué herramientas proporciona iOS WebKit Debug Proxy MCP?
Expone 10 herramientas, incluidas iwdp_status, restart_iwdp, list_devices, list_pages, select_page.
¿Puede depurar Safari en un iPhone real?
Sí. Se conecta a dispositivos iOS mediante USB a través de ios-webkit-debug-proxy y expone el WebKit Inspector Protocol, lo que te permite depurar pestañas reales de Safari y no solo simuladores.
¿Es compatible con Chrome DevTools Protocol?
No. Se enfoca en el WebKit Inspector Protocol, que es incompatible con el CDP utilizado por las herramientas de Chrome DevTools.
¿Puede leer cookies httpOnly?
Sí, lee las cookies a través del protocolo, incluyendo cookies httpOnly y secure que document.cookie no puede ver.
¿Qué necesito tener instalado antes de usarlo?
Instala ios-webkit-debug-proxy (por ejemplo, vía brew), conecta el dispositivo iOS por USB y habilita el Web Inspector en Ajustes → Safari → Avanzado.
¿Qué clientes pueden usarlo?
Cualquier cliente compatible con MCP, incluyendo Claude Code, VS Code, Cursor, Windsurf, Codex CLI, Antigravity y los IDE de JetBrains.