The nightly stress test detected 2 servers with configuration errors (not authentication issues).

Test Summary

• Test Session: stress-test-20260208-034257
• Test Date: 2026-02-08T03:42:57Z
• Total Configuration Failures: 2

Failed Servers

1. filesystem - Command Arguments Error

Container: mcp/filesystem

Issue Type: Configuration Error

Error:

Usage: mcp-server-filesystem (allowed-directory) [additional-directories...]

Analysis:
The filesystem server expects allowed directories as positional command-line arguments, but the configuration is passing them as environment variables (ALLOWED_PATHS). The docker command structure needs to be updated.

Current Configuration Issue:
The server is launched with environment variable but expects positional args.

Suggested Fix:
Update configuration to pass directories as positional arguments:

{
  "filesystem": {
    "type": "stdio",
    "container": "mcp/filesystem",
    "args": ["/workspace", "/additional/path"]
  }
}

Or update the docker args to include the directory paths:

{
  "filesystem": {
    "type": "stdio",
    "command": "docker",
    "args": ["run", "--rm", "-i", "-v", "/tmp/mcp-test-fs:/workspace:rw", "mcp/filesystem", "/workspace"]
  }
}
``````

**Suggested Investigation:**
- [ ] Review filesystem server documentation for correct argument format
- [ ] Update gateway configuration to pass directories correctly
- [ ] Test with simple single directory first
- [ ] Consider if server should be updated to support env vars

---

### 2. playwright - Duplicate Flag Error

**Container:** mcr.microsoft.com/playwright/mcp

**Issue Type:** Configuration Error

**Error:**
``````
error: unknown option '--init'
``````

**Analysis:**
The docker command includes the `--init` flag twice - once as a docker option (correct) and once passed to the playwright binary (incorrect). The playwright binary doesn't recognize the `--init` flag and fails.

**Current Configuration Issue:**
``````
docker run --rm -i --init --network host mcr.microsoft.com/playwright/mcp --output-dir ... --init --network host

Notice --init and --network host appear twice.

Suggested Fix:
Remove the duplicate flags from the playwright server arguments:

{
  "playwright": {
    "type": "stdio",
    "command": "docker",
    "args": [
      "run", "--rm", "-i",
      "--init",
      "--network", "host",
      "-v", "/tmp/gh-aw/mcp-logs:/tmp/gh-aw/mcp-logs:rw",
      "mcr.microsoft.com/playwright/mcp",
      "--output-dir", "/tmp/gh-aw/mcp-logs/playwright",
      "--allowed-hosts", "localhost,localhost:*,127.0.0.1,127.0.0.1:*",
      "--allowed-origins", "localhost;localhost:*;127.0.0.1;127.0.0.1:*"
    ]
  }
}

Suggested Investigation:

• Review playwright MCP server documentation
• Remove duplicate --init and --network host from args array
• Verify correct flag order for playwright binary
• Test with corrected configuration

Gateway Logs

From the gateway logs, both issues are clearly configuration-related, not authentication or protocol issues:

filesystem:

• Server expects CLI args but receives env vars
• Quick fix: restructure docker command args

playwright:

• Duplicate flags passed to both docker and playwright binary
• Quick fix: remove duplicate flags from args array

Test Configuration Used

The test used the following configuration:

• Startup Timeout: 60s
• Tool Timeout: 30s
• Test Method: Sequential server testing
• Gateway: Successfully handled all requests

Impact

These configuration issues prevent 2 MCP servers from launching:

1. filesystem - Would provide file system access if configured correctly
2. playwright - Would provide browser automation if configured correctly

Both are fixable with configuration changes and don't require code modifications.

Next Steps

1. Priority: High - Fix filesystem configuration

   • Update docker args to pass directories as positional arguments
   • Test with /workspace mount

2. Priority: High - Fix playwright configuration

   • Remove duplicate --init and --network host flags
   • Verify flag order matches playwright binary expectations

3. Re-run stress test to verify fixes

4. Update documentation with correct configuration examples

Generated by Nightly MCP Stress Test
Test Session: stress-test-20260208-034257

Full Test Results: See workflow run artifacts at /tmp/mcp-stress-results/

AI generated by Nightly MCP Server Stress Test