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

scout-mcp-server

v1.0.0

Published

MCP server for Claude Code integration with Scout - AI-powered test management and bug tracking

Readme

@anthropic/scout-mcp-server

MCP (Model Context Protocol) server that enables Claude Code to integrate with Scout for bug tracking and test case management.

Features

  • List and view bugs from Scout with full context (console errors, network errors, screenshots)
  • Update bug status directly from Claude Code after fixing issues
  • Create test cases for new features or bug regression tests
  • Access project information including codebase paths for navigation

Quick Setup

1. Add Configuration to Your Project

Create a .mcp.json file in your project's root directory:

{
  "mcpServers": {
    "scout": {
      "command": "npx",
      "args": ["-y", "@anthropic/scout-mcp-server"],
      "env": {
        "SCOUT_API_URL": "http://localhost:4002"
      }
    }
  }
}

2. Start Claude Code

Run Claude Code from your project directory:

cd your-project
claude

Claude Code will detect the .mcp.json and prompt you to approve the Scout MCP server.

Environment Variables

| Variable | Description | Default | |----------|-------------|---------| | SCOUT_API_URL | URL of the Scout API server | http://localhost:4002 |

Optional: Set Git Repository in Scout

For each project in Scout, you can configure the Git Repository in Project Settings:

  1. Go to Projects → Select a project
  2. Click the gear icon (⚙️) in the header
  3. Enter your repository URL (e.g., github.com/myorg/myapp)
  4. Optionally set the default branch (e.g., main, develop)
  5. Save settings

This allows Claude Code to verify it's working in the correct repository before making changes.

Available Tools

scout_list_projects

List all projects in Scout with their IDs, names, target URLs, and repository info.

scout_get_project

Get detailed information about a specific project including test suites.

Parameters:

  • projectId (required): The project ID

scout_list_bugs

List bugs with optional filtering.

Parameters:

  • projectId (optional): Filter by project
  • status (optional): Filter by status (NEW, CONFIRMED, IN_PROGRESS, BLOCKED, RESOLVED, WONT_FIX, DUPLICATE)
  • severity (optional): Filter by severity (BLOCKER, CRITICAL, MAJOR, MINOR, TRIVIAL)

scout_get_bug

Get full bug details including debugging context.

Parameters:

  • bugId (required): The bug ID

Returns:

  • Title, description, severity, status
  • Console errors captured at bug time
  • Network errors captured at bug time
  • Page URL where bug occurred
  • Screenshot URL (if available)
  • Related test case and step
  • Session recording info

scout_update_bug

Update a bug's status or assignment.

Parameters:

  • bugId (required): The bug ID
  • status (optional): New status
  • assignedDevId (optional): Developer ID to assign

scout_list_test_cases

List test cases with optional filtering.

Parameters:

  • projectId (optional): Filter by project
  • suiteId (optional): Filter by test suite

scout_create_test_case

Create a new test case.

Parameters:

  • suiteId (required): Test suite ID
  • code (required): Test case code (e.g., "TC-042")
  • title (required): Test case title
  • expectedResult (required): Expected outcome
  • description (optional): Detailed description
  • preconditions (optional): Prerequisites
  • priority (optional): CRITICAL, HIGH, MEDIUM, LOW
  • section (optional): Category for grouping
  • steps (optional): Array of test steps

scout_list_test_suites

List test suites for a project.

Parameters:

  • projectId (required): The project ID

scout_create_test_suite

Create a new test suite.

Parameters:

  • projectId (required): The project ID
  • name (required): Suite name
  • version (optional): Version identifier

Usage Examples

Debugging a Bug

User: "Debug the login bug in Scout"

Claude Code:
1. scout_list_bugs(status="NEW") → finds login-related bug
2. scout_get_bug(bugId="...") → gets console errors, network failures
3. Reads codebase files based on error stack traces
4. Identifies and fixes the issue
5. scout_update_bug(bugId="...", status="RESOLVED")

Creating Test Coverage

User: "Add test cases for the new user registration feature"

Claude Code:
1. scout_list_projects() → finds project
2. scout_list_test_suites(projectId="...") → finds appropriate suite
3. scout_create_test_case(...) → creates test cases for:
   - Valid registration
   - Invalid email format
   - Password requirements
   - Duplicate email handling

Development

# Run in development mode
pnpm dev

# Build for production
pnpm build

# Start production server
pnpm start

Troubleshooting

"Scout API error: Connection refused"

Ensure the Scout API server is running on the configured port:

cd apps/api
pnpm dev

Tools not appearing in Claude Code

  1. Verify the MCP server is built: pnpm build
  2. Check the path in claude_desktop_config.json is correct
  3. Restart Claude Code after config changes