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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rapidtriageme/mcp

v4.0.0

Published

YarlisAISolutions RapidTriage MCP - AI-powered browser debugging and triage platform using Model Context Protocol with Cloud Run support

Readme

RapidTriage MCP Server

Model Context Protocol server for AI-powered browser debugging and triage

npm version License: MIT MCP Compatible

Table of Contents

Overview

RapidTriage MCP Server implements the Model Context Protocol (MCP) to give AI assistants browser debugging, testing, and audit capabilities. It works with any MCP-compatible IDE or AI platform.

The server supports three transport modes:

| Transport | Use Case | IDEs | |-----------|----------|------| | stdio (default) | Local IDE integration | Claude Code, Cursor, Windsurf, VS Code, JetBrains | | SSE | Remote / networked connections | Any MCP client supporting SSE | | Streamable HTTP | Newer MCP spec, stateless HTTP | Clients implementing the streamable HTTP spec |

Quick Start

# Start the MCP server (stdio mode, used by most IDEs)
npx @rapidtriageme/mcp

Then configure your IDE using one of the sections below.

Installation

Using npx (Recommended)

No installation required. IDEs will run it automatically:

npx @rapidtriageme/mcp

Global Installation

npm install -g @rapidtriageme/mcp

Local Development

git clone https://github.com/YarlisAISolutions/rapidtriageME.git
cd rapidtriageME/rapidtriage-mcp
npm install
npm run build
npm start

Transports

stdio (Default)

Standard input/output. This is the default transport and what all major IDEs use for local MCP servers. No additional configuration needed.

npx @rapidtriageme/mcp
# or explicitly:
npx @rapidtriageme/mcp --transport=stdio

SSE (Server-Sent Events)

Runs an HTTP server that accepts SSE connections. Useful when the MCP server runs on a remote machine or container.

npx @rapidtriageme/mcp --transport=sse
# or via environment variable:
MCP_TRANSPORT=sse npx @rapidtriageme/mcp

Default port is 3100. Override with:

MCP_HTTP_PORT=8080 npx @rapidtriageme/mcp --transport=sse

Endpoints:

  • GET /sse -- SSE connection endpoint
  • POST /messages?sessionId=<id> -- JSON-RPC message endpoint
  • GET /health -- Health check

Streamable HTTP

Newer MCP transport using stateless HTTP POST requests.

npx @rapidtriageme/mcp --transport=http
# or via environment variable:
MCP_TRANSPORT=http npx @rapidtriageme/mcp

Endpoints:

  • POST /mcp -- JSON-RPC request/response
  • GET /mcp -- Server-initiated notifications (SSE)
  • GET /health -- Health check

IDE Integration

Claude Code

Claude Code uses stdio transport natively. Add the following to your project's .mcp.json file, or configure globally with claude mcp add.

Option A: Project config (.mcp.json in project root):

{
  "mcpServers": {
    "rapidtriage": {
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

Option B: CLI:

claude mcp add rapidtriage -- npx @rapidtriageme/mcp

Reference config: ide-configs/claude-code.json


Cursor

Cursor supports MCP servers via its settings. Add the configuration to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-level).

{
  "mcpServers": {
    "rapidtriage": {
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

After saving, restart Cursor. The RapidTriage tools will appear in the AI chat.

Reference config: ide-configs/cursor-settings.json


Windsurf

Windsurf uses the same MCP config format. Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "rapidtriage": {
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

Restart Windsurf after saving. Tools will be available in Cascade.

Reference config: ide-configs/windsurf-settings.json


VS Code (GitHub Copilot)

VS Code supports MCP servers through GitHub Copilot's agent mode. Add to your workspace .vscode/settings.json or user settings:

{
  "mcp": {
    "servers": {
      "rapidtriage": {
        "type": "stdio",
        "command": "npx",
        "args": ["@rapidtriageme/mcp"],
        "env": {
          "RAPIDTRIAGE_API_KEY": "your-key"
        }
      }
    }
  }
}

Alternatively, create a .vscode/mcp.json file in your project:

{
  "servers": {
    "rapidtriage": {
      "type": "stdio",
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

After saving, open GitHub Copilot chat in Agent mode (@workspace). The RapidTriage tools will be listed under available tools.

Reference config: ide-configs/vscode-settings.json


JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)

JetBrains IDEs support MCP through the AI Assistant plugin (2025.1+). Configure in Settings > Tools > AI Assistant > MCP Servers, or add a mcp.json file to your project root:

{
  "mcpServers": {
    "rapidtriage": {
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

Restart the IDE after configuration. Tools appear in the AI Assistant chat.

Reference config: ide-configs/jetbrains-settings.json


Claude Desktop

Edit the Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "rapidtriage": {
      "command": "npx",
      "args": ["@rapidtriageme/mcp"],
      "env": {
        "RAPIDTRIAGE_API_KEY": "your-key"
      }
    }
  }
}

Restart Claude Desktop after saving.


Remote / SSE Connections

For IDEs or clients that support remote MCP connections via SSE, first start the server in SSE mode:

MCP_HTTP_PORT=3100 npx @rapidtriageme/mcp --transport=sse

Then point your MCP client to:

SSE URL:     http://your-server:3100/sse
Message URL: http://your-server:3100/messages

For Streamable HTTP clients:

MCP_HTTP_PORT=3100 npx @rapidtriageme/mcp --transport=http
MCP URL: http://your-server:3100/mcp

Available Tools

Browser Debugging

| Tool | Description | |------|-------------| | getConsoleLogs | Retrieve all browser console logs | | getConsoleErrors | Retrieve browser console errors only | | getNetworkLogs | Retrieve all network request/response logs | | getNetworkErrors | Retrieve failed network requests | | getSelectedElement | Get the currently selected DOM element | | takeScreenshot | Capture a screenshot of the current browser tab | | wipeLogs | Clear all stored browser logs from memory |

Audits

| Tool | Description | |------|-------------| | runAccessibilityAudit | Run WCAG accessibility compliance audit | | runPerformanceAudit | Run Core Web Vitals and performance audit | | runSEOAudit | Run SEO analysis audit | | runBestPracticesAudit | Run security and best practices audit |

Workflow Tools

| Tool | Description | |------|-------------| | runDebuggerMode | Start a guided debugging workflow | | runAuditMode | Run all audits in sequence with analysis | | runNextJSAudit | SEO audit procedures specific to Next.js apps |

Configuration

Environment Variables

# Browser tools server connection
BROWSER_TOOLS_URL=https://your-server.run.app   # Full URL (Cloud Run / remote)
BROWSER_TOOLS_HOST=127.0.0.1                     # Local server host
BROWSER_TOOLS_PORT=3025                          # Local server port
BROWSER_TOOLS_MODE=auto                          # auto | local | cloudrun | custom

# MCP transport configuration
MCP_TRANSPORT=stdio                              # stdio | sse | http
MCP_HTTP_PORT=3100                               # Port for SSE / HTTP transports

# API authentication
RAPIDTRIAGE_API_KEY=your-key                     # API key for authenticated access

# Debugging
DEBUG=true                                        # Enable debug logging

CLI Flags

npx @rapidtriageme/mcp --transport=stdio     # Use stdio transport (default)
npx @rapidtriageme/mcp --transport=sse       # Use SSE transport
npx @rapidtriageme/mcp --transport=http      # Use Streamable HTTP transport

API Reference

Protocol

The MCP server communicates using JSON-RPC 2.0. The transport determines how messages are delivered.

Request Format

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "getConsoleLogs",
    "arguments": {}
  },
  "id": 1
}

Response Format

{
  "jsonrpc": "2.0",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "[ ... log entries ... ]"
      }
    ]
  },
  "id": 1
}

Tool Discovery

Clients can list available tools by sending:

{
  "jsonrpc": "2.0",
  "method": "tools/list",
  "params": {},
  "id": 1
}

The response includes each tool's name, description, and input schema (JSON Schema), which IDEs use for auto-completion and validation.

Troubleshooting

Server Connection Failed

# Verify the browser tools server is running
curl http://localhost:3025/.identity

# If using Cloud Run, check the remote endpoint
curl https://your-server.run.app/.identity

MCP Server Not Found in IDE

  1. Restart your IDE after changing MCP configuration.
  2. Verify Node.js is in your PATH: node --version (requires 18+).
  3. Test manually: npx @rapidtriageme/mcp -- it should start without errors.
  4. If npx is not found, use the absolute path:
    {
      "command": "/usr/local/bin/npx",
      "args": ["@rapidtriageme/mcp"]
    }

SSE Transport Not Connecting

  1. Confirm the server started on the expected port: check the console output for the URL.
  2. Verify the port is not blocked by a firewall.
  3. Test the health endpoint: curl http://localhost:3100/health

Tools Not Appearing in IDE

  1. Some IDEs require you to explicitly enable MCP or agent mode.
  2. In VS Code, switch Copilot chat to Agent mode.
  3. In JetBrains, ensure the AI Assistant plugin is updated to 2025.1+.
  4. Check IDE logs for MCP connection errors.

Debug Mode

Enable verbose logging:

DEBUG=true npx @rapidtriageme/mcp

Contributing

See the Contributing Guide.

git clone https://github.com/YarlisAISolutions/rapidtriageME.git
cd rapidtriageME/rapidtriage-mcp
npm install
npm run build
npm start

Support

License

MIT - YarlisAISolutions