Browser Echo MCP

browser-echo makes it easy for you to read client-side logs directly in your coding agent during development.

Features

🤖 AI Coding Assistant Support - Perfect for Cursor AI, Claude Code, GitHub Copilot CLI, Gemini CLI, and other code editors that read terminal output

🚀 Framework Support - React, Vue, Nuxt 3/4, Next.js, TanStack Start, Vite-based frameworks, and custom setups

Quick start

1. Install Framework Package

First, set up Browser Echo for your framework:

Framework	Quick Setup
TanStack / Vite	Installation Guide
Nuxt 3/4	Installation Guide
Next.js (App Router)	Installation Guide
Vue + Vite	Installation Guide
React + Vite	Installation Guide
Vue (non-Vite)	Installation Guide
React (non-Vite)	Installation Guide
Core	Installation Guide

2. Use Browser Echo MCP

⚠️ IMPORTANT: You must complete step 1 (framework setup) first before MCP will work. The MCP server needs your frameworks server to forward browser logs to it.

📖 Set up Browser Echo MCP Server for AI assistant integration

Browser Echo Core (Terminal only)

Stream browser console.* logs to your dev terminal and optional file logging.

browser-echo makes it easy for you (and your AI coding assistant) to read client-side logs directly in the server terminal during development.

💡 Tip: The MCP server isn't required for most use cases. AI assistants are usually smart enough to read CLI output directly, and the terminal solution is often faster and cheaper than MCP integration. The MCP was designed to avoid polluting the context window, but in most cases the terminal output is sufficient.

• Drop‑in client patch that wraps console.log/info/warn/error/debug
• Batched posts (uses sendBeacon when possible)
• Source hints (file:line:col) + stack traces
• Colorized terminal output
• Optional file logging (Vite provider only)
• Works great with AI assistants reading your terminal
• Optional network capture (opt‑in): fetch, XMLHttpRequest, WebSocket

Production

No production impact. Providers enable this across frameworks by injecting a tiny client patch and exposing a dev-only HTTP endpoint.

• Providers apply only in development and inject nothing into your production client bundles.
• If you also want to strip console.* in prod builds, use your bundler’s strip tools (e.g. Rollup plugin) separately.

FAQ / Troubleshooting

The MCP doesn't show any logs

1. Make sure you have installed framework support → See Install Framework Package above
2. Ensure your development server is running before starting the MCP server
3. Restart the MCP server if logs still don't appear:
   • In Cursor: Settings → MCP & Integrations → toggle "browser-echo" off and on
   • In Claude Code: Type /mcp → Choose "browser-echo" → Enter → Hit 2 to reconnect

No logs appear (framework setup issues)