MCP server for Claude Code integration with Scout - AI-powered test management and bug tracking
npm install scout-mcp-serverMCP (Model Context Protocol) server that enables Claude Code to integrate with Scout for bug tracking and test case management.
- 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
Create a .mcp.json file in your project's root directory:
``json`
{
"mcpServers": {
"scout": {
"command": "npx",
"args": ["-y", "@anthropic/scout-mcp-server"],
"env": {
"SCOUT_API_URL": "http://localhost:4002"
}
}
}
}
Run Claude Code from your project directory:
`bash`
cd your-project
claude
Claude Code will detect the .mcp.json and prompt you to approve the Scout MCP server.
| Variable | Description | Default |
|----------|-------------|---------|
| SCOUT_API_URL | URL of the Scout API server | http://localhost:4002 |
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.
Parameters:
- projectId (required): The project ID
Parameters:
- projectId (optional): Filter by projectstatus
- (optional): Filter by status (NEW, CONFIRMED, IN_PROGRESS, BLOCKED, RESOLVED, WONT_FIX, DUPLICATE)severity
- (optional): Filter by severity (BLOCKER, CRITICAL, MAJOR, MINOR, TRIVIAL)
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
Parameters:
- bugId (required): The bug IDstatus
- (optional): New statusassignedDevId
- (optional): Developer ID to assign
Parameters:
- projectId (optional): Filter by projectsuiteId
- (optional): Filter by test suite
Parameters:
- suiteId (required): Test suite IDcode
- (required): Test case code (e.g., "TC-042")title
- (required): Test case titleexpectedResult
- (required): Expected outcomedescription
- (optional): Detailed descriptionpreconditions
- (optional): Prerequisitespriority
- (optional): CRITICAL, HIGH, MEDIUM, LOWsection
- (optional): Category for groupingsteps
- (optional): Array of test steps
Parameters:
- projectId (required): The project ID
Parameters:
- projectId (required): The project IDname
- (required): Suite nameversion
- (optional): Version identifier
`
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")
`
`
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
`
`bashRun in development mode
pnpm dev
Troubleshooting
$3
Ensure the Scout API server is running on the configured port:
`bash
cd apps/api
pnpm dev
`$3
1. Verify the MCP server is built: pnpm build`