@rapidtriageme/mcp
v4.0.0
Published
YarlisAISolutions RapidTriage MCP - AI-powered browser debugging and triage platform using Model Context Protocol with Cloud Run support
Maintainers
Readme
RapidTriage MCP Server
Model Context Protocol server for AI-powered browser debugging and triage
Table of Contents
- Overview
- Quick Start
- Installation
- Transports
- IDE Integration
- Available Tools
- Configuration
- API Reference
- Troubleshooting
- Contributing
- License
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/mcpThen configure your IDE using one of the sections below.
Installation
Using npx (Recommended)
No installation required. IDEs will run it automatically:
npx @rapidtriageme/mcpGlobal Installation
npm install -g @rapidtriageme/mcpLocal Development
git clone https://github.com/YarlisAISolutions/rapidtriageME.git
cd rapidtriageME/rapidtriage-mcp
npm install
npm run build
npm startTransports
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=stdioSSE (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/mcpDefault port is 3100. Override with:
MCP_HTTP_PORT=8080 npx @rapidtriageme/mcp --transport=sseEndpoints:
GET /sse-- SSE connection endpointPOST /messages?sessionId=<id>-- JSON-RPC message endpointGET /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/mcpEndpoints:
POST /mcp-- JSON-RPC request/responseGET /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/mcpReference 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=sseThen point your MCP client to:
SSE URL: http://your-server:3100/sse
Message URL: http://your-server:3100/messagesFor Streamable HTTP clients:
MCP_HTTP_PORT=3100 npx @rapidtriageme/mcp --transport=httpMCP URL: http://your-server:3100/mcpAvailable 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 loggingCLI 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 transportAPI 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/.identityMCP Server Not Found in IDE
- Restart your IDE after changing MCP configuration.
- Verify Node.js is in your PATH:
node --version(requires 18+). - Test manually:
npx @rapidtriageme/mcp-- it should start without errors. - If npx is not found, use the absolute path:
{ "command": "/usr/local/bin/npx", "args": ["@rapidtriageme/mcp"] }
SSE Transport Not Connecting
- Confirm the server started on the expected port: check the console output for the URL.
- Verify the port is not blocked by a firewall.
- Test the health endpoint:
curl http://localhost:3100/health
Tools Not Appearing in IDE
- Some IDEs require you to explicitly enable MCP or agent mode.
- In VS Code, switch Copilot chat to Agent mode.
- In JetBrains, ensure the AI Assistant plugin is updated to 2025.1+.
- Check IDE logs for MCP connection errors.
Debug Mode
Enable verbose logging:
DEBUG=true npx @rapidtriageme/mcpContributing
See the Contributing Guide.
git clone https://github.com/YarlisAISolutions/rapidtriageME.git
cd rapidtriageME/rapidtriage-mcp
npm install
npm run build
npm startSupport
- Email: [email protected]
- Issues: GitHub Issues
- Docs: rapidtriage.me/docs
License
MIT - YarlisAISolutions
