npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@realmikekelly/react-native-logs-mcp

v1.0.1

Published

An MCP server that connects to your React Native application debugger (fork optimized for AI context efficiency)

Downloads

22

Readme

React Native Logs MCP

An MCP server that connects to your React Native application debugger via the Chrome DevTools Protocol.

This is a fork of twodoorsdev/react-native-debugger-mcp optimized to minimize AI context usage by reducing verbose output. Console logs are returned as plain text rather than JSON, and stack traces are only included for errors and warnings.

✨ Key Features

  • Token-Efficient Output: Console logs are formatted as plain text (one per line) instead of verbose JSON, reducing context usage by ~98%

  • Smart Stack Traces: Full stack traces are only included for errors and warnings, not for regular log messages

  • Complete Console Log Retrieval: Captures full console output from Metro bundler including:

    • Multi-line strings and template literals
    • Complete object structures with nested properties
    • Arrays with all elements and their types
    • Complex data structures (Maps, Sets, Dates, etc.)
    • Error objects with full stack traces
    • All console levels (log, info, warn, error, debug)
  • Enhanced Formatting: Uses Chrome DevTools Protocol's rich formatting to preserve:

    • Original object structure and formatting
    • Multi-line content without truncation
    • Proper type representation for all JavaScript values
    • Readable output for debugging complex applications

🚀 Quick Start

Add the following to your Claude Desktop/Cursor MCP config:

{
	"mcpServers": {
		"react-native-logs-mcp": {
			"command": "npx",
			"args": ["-y", "react-native-logs-mcp"]
		}
	}
}

🔧 Available Tools

getConnectedApps

Retrieves a list of React Native applications currently connected to the Metro bundler.

Parameters:

  • metroServerPort (number): The port number of the Metro server (default: 8081)

Returns: Array of connected app objects with WebSocket debugger URLs.

readConsoleLogsFromApp

Reads console logs from a connected React Native application through the Chrome DevTools Protocol.

Parameters:

  • app (object): App object returned by getConnectedApps
  • maxLogs (number, optional): Maximum number of logs to return (default: 100)

Returns: Plain text console output with one log per line. Errors and warnings are prefixed with ❌ ERROR: or ⚠️ WARNING: and include the top stack frame for context.

📋 Example Usage

  1. Get connected apps:

    Call getConnectedApps with metroServerPort: 8081
  2. Read console logs:

    Call readConsoleLogsFromApp with the app object and desired maxLogs