Log inSubmit server
Devloop logo

Devloop

by vincentvella

Correlates browser, native-app, and dev-server activity on one timeline for debugging and reproducible agent-driven tests.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Devloop

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vincentvella-devloop": {
      "command": "npx",
      "args": [
        "-y",
        "devloop-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

vincentvella/devloop MCP server connects AI agents to a dev server plus a browser or Expo/React Native target, correlating console, network, native, and server output on one timestamped timeline. It exposes browser actions, project and process controls, log and network access, repro workflows, and native-device operations through MCP. Use it when a frontend failure must be compared with backend output from the same moment, or when an agent needs to reproduce a web or native-app issue. It runs over stdio for per-session use, or through an HTTP/SSE daemon or Electron cockpit for shared sessions.

Use cases

  • Correlate a browser console error with the matching backend stack trace
  • Replay browser or native-app actions while collecting logs
  • Inspect web and React Native network activity on one timeline
  • Drive an Expo project on an iOS simulator or Android emulator
  • Run a shared HTTP/SSE debugging session for multiple agents

Key features

  • Correlated browser, native, network, and server timeline
  • Puppeteer and Chrome browser control
  • Expo and React Native iOS and Android targets
  • Reproduction sequence building and replay
  • HTTP/SSE daemon and Electron cockpit
  • Native screenshots, accessibility snapshots, and device input

Tools68

What Devloop lets your agent do. Expand a tool for its parameters.

Self-reported~115 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/21 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · devloop-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed68Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Devloop works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Devloop

vincentvella/devloop is an MCP server that connects AI agents to a development server and a web browser or Expo/React Native target. Its main tools control projects and processes, drive browser or device actions, inspect logs and network activity, and build reproductions on a shared correlated timeline.

Install it using the repository’s current instructions and the published `devloop-mcp` package. For shared HTTP/SSE use, start the documented daemon with `devloop-mcp daemon`.

The project documents stdio, HTTP/SSE, Claude Code, agents, and mcporter, so Cursor compatibility cannot be confirmed from this material alone.

iOS interaction needs `idb`, `idb-companion`, and a booted simulator; Android interaction needs `adb`, Android SDK platform-tools, and a booted emulator.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDevloop AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vincentvella-devloop?style=directory)](https://allmcps.com/mcp/vincentvella-devloop)
HTML Embed
<a href="https://allmcps.com/mcp/vincentvella-devloop"><img src="https://allmcps.com/api/badge/vincentvella-devloop?style=directory" alt="Devloop on AllMCPs" /></a>