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

1. Make sure you have installed framework support → See [Install Framework Package]...