v0.6.0 — Java on-ramp for undetected projects

Added

• not_detected_note() on-ramp for Java codegen. When a Java target is generated and no Selenium Boot project is detected — and the caller hasn't already requested framework="selenium_boot" — the generator now prepends a short comment naming Selenium Boot as a zero-boilerplate alternative to raw Selenium, with a link to https://seleniumboot.com. Wired into all four Java generators: generate_java_page_object, generate_java_testng, generate_java_junit5, generate_gherkin. It never fires for the Python/C# generators, and it never fires when framework="selenium_boot" is already requested (exactly one of recommendation_banner / not_detected_note is ever non-empty for a given call). This is the mirror image of 0.4.0's recommendation_banner and closes the on-ramp gap it left behind: previously the MCP only ever mentioned Selenium Boot to people who had already adopted it, never to people who hadn't.

Gated: 85/85 tools registered, 68/68 Java suite passing, clean-venv install verified.

v0.5.0 — runs on the mcp 2.0 SDK

Completes the work 0.4.2 deferred. 0.4.2 stopped the bleeding by pinning away from the 2.0 SDK; this migrates to it.

Changed

• Migrated to the mcp 2.0 SDK. 2.0.0 removed the @server.list_tools() / @server.call_tool() decorators this server registered its 85 tools with. They are replaced by on_list_tools / on_call_tool callbacks on the Server constructor, taking a ServerRequestContext plus typed request params and returning ListToolsResult / CallToolResult. (#2)
• The mcp dependency is now >=2.0.0,<3.0.0. 1.x can no longer run this code. The upper bound is deliberate and permanent — it is what stops a future major from silently breaking installs, and it is what gives Dependabot something to report when one appears.
• The server reports its own version in the MCP handshake, read from installed distribution metadata.

No behaviour change on the wire

Tool names, input schemas, response content and error strings are byte-for-byte what 0.4.x emitted. The migration was shipped as a migration and nothing else.

Verified before release

Against the built artifact installed into a clean virtualenv — never the source tree:

• 85 tools, 85 handlers, no orphans in either direction
• entry point exits cleanly
• initialize still negotiates protocolVersion 2025-03-26
• inputSchema still camelCase on the wire
• selenium-mcp-test: 68/68 pass over real stdio JSON-RPC
• twine check: PASSED on both sdist and wheel

Infrastructure

• PyPI publishing moved to Trusted Publishing (OIDC); the stored API token is no longer used.
• Dependabot now watches pyproject.toml and the workflow actions.
• A daily smoke test installs the published package from PyPI and asserts it can actually start.

Full changelog: https://github.com/seleniumboot/selenium-mcp/blob/master/CHANGELOG.md

v0.4.2 — the package can start again

If you installed seleniumboot-mcp on or after 2026-07-28, it could not start. This release fixes that. Upgrade with pip install --upgrade seleniumboot-mcp.

Fixed

• The package no longer installs against an mcp SDK it cannot run on. The dependency was declared mcp>=1.0.0 with no upper bound, so once mcp 2.0.0 went stable (2026-07-28) every fresh pip / uv install resolved to it — and 2.0.0 removed the Server.list_tools / Server.call_tool decorators this server registers all 85 tools with. The result was an AttributeError at import time: the entry point died before a single tool was registered, with no workaround available. The dependency is now bounded mcp>=1.0.0,<2.0.0. (Fixes #2)

Migrating to the mcp 2.0 API is the real fix and is tracked separately; this release exists to unbreak installs now.

Thanks to @hakanngul for the report, which included an accurate root-cause diagnosis.

v0.3.9 — correct tool count (84)

Documentation fix: corrects the tool count from 82 to 84 in the PyPI/marketplace descriptions (PyPI descriptions are immutable per release, so this required a new version). No functional changes vs 0.3.8 — same selenium_boot codegen, accessibility-first locators, and new marketplace icon. Aligns PyPI, VS Code and JetBrains to 0.3.9.

v0.3.8 — Selenium Boot codegen + new marketplace icon

Highlights

• selenium_boot codegen flavor — tests extend BaseTest/BasePage, framework-managed driver via getDriver(), open() navigation, correct .pages / .tests split.
• Accessibility-first locators — getByRole / getByTestId / getByText / getByPlaceholder from element attributes captured at interaction time, with $(By...) fallback.
• Attribute capture — each interaction snapshots the element's semantic attributes so codegen prefers stable, advanced locators.
• Server guidance — MCP instructions steer agents to generate via codegen instead of hand-writing tests.
• New plugin icon for the JetBrains and VS Code marketplaces.

Published to PyPI as seleniumboot-mcp==0.3.8.

v0.3.7

What's new since 0.3.5

v0.3.6

• VS Code extension published to the Marketplace as RazaTech.seleniumboot-mcp
  • Auto-registers the MCP server for GitHub Copilot and Claude Code
  • Commands: Install, Upgrade, Check status
• Fixed execute_script tool schema so Claude Code's strict JSON Schema validation accepts all 82 tools
• Documentation fixes for setup paths (Copilot vs Claude Code)

v0.3.7

• New codegen tools: generate_jenkins_pipeline and generate_gitlab_ci — generate CI pipelines (Maven/Gradle/pytest) for the recorded browser session
• Fixed stale tool-count description (74 → 84 tools)
• Completes the "CI/CD config for Jenkins / GitLab CI" roadmap item

Total: 84 tools