Align checked-in .mcp.json files with documented Claude Code setup

[boysugi20]

Summary

The Claude Code instructions in mcp_servers/README.md describe the checked-in .mcp.json as running the server through:

{
  "command": "uv",
  "args": ["run", "seleniumbase-mcp"]
}

However, both the repository-root .mcp.json and mcp_servers/.mcp.json currently invoke the console script directly:

{
  "command": "seleniumbase-mcp",
  "args": []
}

This makes the documented clone-based setup inconsistent with the checked-in configuration.

Reproduction

1. Clone the SeleniumBase repository.
2. Run:

   cd mcp_servers
   uv sync

3. Launch Claude Code using the checked-in .mcp.json.

uv sync installs seleniumbase-mcp inside the project's virtual environment, but does not normally place that executable on the shell's global PATH. The checked-in configuration therefore requires an additional global/package installation that the clone-based Claude Code section does not specify.

Expected behavior

A fresh clone configured according to the README should be able to launch the MCP server without requiring a separate global installation.

Possible resolution

If the clone-based workflow is intended, the configurations could invoke uv explicitly:

Repository-root .mcp.json:

{
  "mcpServers": {
    "seleniumbase-mcp": {
      "type": "stdio",
      "command": "uv",
      "args": ["--directory", "mcp_servers", "run", "seleniumbase-mcp"]
    }
  }
}

mcp_servers/.mcp.json:

{
  "mcpServers": {
    "seleniumbase-mcp": {
      "type": "stdio",
      "command": "uv",
      "args": ["run", "seleniumbase-mcp"]
    }
  }
}

If the direct seleniumbase-mcp command is intentional, the README could instead state that pip install "seleniumbase[mcp]" or uv tool install . is required before using the checked-in configuration.

I would be happy to submit the corresponding documentation/configuration update once the preferred behavior is confirmed.