# vincentvella/devloop [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/vincentvella/devloop  
**GitHub Stars:** 2  
**npm Downloads (last month):** 1061  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vincentvella-devloop

## Description
Drives a browser (or a native Expo/React Native app on iOS/Android) and your dev server onto one correlated timeline, so a browser console error and the backend stack trace from the same moment line up. Includes repro action sequences, a unified log/network query API, and an Electron cockpit.

## Tools
Capabilities this server exposes over MCP:

- **project**
- **cmd**
- **cwd**
- **package.json**
- **dev**
- **develop**
- **web**
- **start**
- **serve**
- **metro**
- **hard**
- **Enter**
- **Escape**
- **Tab**
- **ArrowDown**
- **device**
- **iphone**
- **ipad**
- **pixel**
- **reset**
- **slow-3g**
- **fast-3g**
- **offline**
- **none**
- **ref**
- **browser_click**
- **browser_type**
- **source**
- **server**
- **browser**
- **stream**
- **stdout**
- **stderr**
- **console**
- **network**
- **pageerror**
- **app**
- **pane_list**
- **seq**
- **sinceSeq**
- **windowMs**
- **DEVLOOP_NET_THRESHOLD**
- **detail**
- **get_logs**
- **resolvedStack**
- **error.stack**
- **byStream**
- **errors**
- **navigate**
- **click**
- **type**
- **hover**
- **scroll**
- **select**
- **press**
- **eval**
- **wait**
- **action**
- **stepSettleMs**
- **settleMs**
- **idleMs**
- **timeoutMs**
- **waitNote**
- **continueOnError**
- **stoppedAtStep**
- **steps**
- **repro**
- **id**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "devloop": {
    "command": "npx",
    "args": ["-y","devloop-mcp"]
  }
}
```

## Documentation

## What vincentvella/devloop does

vincentvella/devloop MCP server provides an MCP tool layer for driving a development project while collecting related runtime evidence. Its supported targets include Chrome-based web applications and Expo/React Native applications on iOS and Android. Browser console messages, page errors, network activity, server stdout and stderr, and native device logs are placed on a shared monotonic timeline.

That timeline is useful when an agent needs to connect a visible failure with the backend event that caused it. The project and process controls can start or inspect a development workflow, while browser actions can click, type, press keys, inspect a page, and select targets. Reproduction sequences can be assembled and replayed rather than described only in text.

## How it works

The server has a shared core behind multiple transports. A stdio process uses Puppeteer with Chrome and is normally spawned for one session. The daemon provides a long-running HTTP/SSE instance, and the Electron cockpit also serves the MCP tools over HTTP/SSE. HTTP transports can accept multiple client sessions while using one shared backend.

In the cockpit, web panes use Electron views controlled through CDP. Native projects use Metro and the Hermes inspector for JavaScript console and error data. Native network requests can be captured into the same timeline, while iOS and Android logs are added as a native source.

## Setup and configuration

The repository publishes the `devloop-mcp` npm package and documents a daemon command, `devloop-mcp daemon`, for starting the shared HTTP/SSE mode. The material provided does not specify a complete package installation command or MCP client configuration block, so those details should be taken from the repository’s current installation instructions.

Native operation has additional host requirements. Embedded iOS interaction requires `idb` and its companion; the README gives Homebrew and `pipx` installation commands and warns that Python 3.14 or newer breaks `fb-idb`. Android interaction requires Android SDK platform-tools with `adb` and a booted emulator. Screenshots and observation can work without the interaction tooling. The embedded iOS simulator mirror is vendored in the cockpit and does not require a first-run download.

## Tools and capabilities

The exposed MCP surface includes:

- Project, working-directory, package metadata, and development-process controls such as `project`, `cwd`, `package.json`, `dev`, `develop`, `start`, `serve`, and `metro`.
- Browser and target controls including `browser`, `browser_click`, `browser_type`, `browser_snapshot` where supported by the active target, `device`, `iphone`, `ipad`, and `pixel`.
- Keyboard actions such as Enter, Escape, Tab, and ArrowDown, plus network-condition choices including `slow-3g`, `fast-3g`, `offline`, and `none`.
- Timeline and debugging access represented by `source`, `server`, and `ref`, along with browser-driving and reproduction workflows.

The active target gates capabilities, so web-only or native-only actions are not expected to be sent to an incompatible substrate. On native targets, interactions can use accessibility references or labels, and the same action sequence can be replayed through the reproduction flow.

## Limitations and notes

Android requires a usable emulator and Android tooling for interaction. The native readiness check can identify missing components, but observation does not imply that taps, typing, or other device actions are available.

The stdio transport reserves stdout for MCP protocol traffic; human-readable output is written to stderr. Client compatibility should therefore be verified against the client’s stdio or HTTP/SSE support.

_Full upstream README: https://allmcps.com/mcp/vincentvella-devloop/readme_