lite-locator-mcp
Playwright MCP with a semantic element finder in front. The proxy runs Playwright MCP as a child process and exposes
all of its tools unchanged, plus browser_find_element(step). That tool takes the accessibility snapshot inside the
proxy, ranks the elements against the test step with small local models, and returns only a shortlist with refs. The
LLM acts on a ref (browser_click target=e990) and calls browser_snapshot only when nothing in the shortlist fits.
Measured on the hard held-out test set (2,875 steps, 38 sites never seen in training), the correct element was in a
shortlist of about 150–500 tokens 82–90% of the time. The full page averaged 12,229 tokens. Playwright MCP is started
with --snapshot-mode none, so clicks and typing no longer return a full snapshot each time.
Install
Needs Python 3.10+ and Node 18+ (for Playwright MCP itself).
pip install lite-locator-mcp # or: uv tool install lite-locator-mcp
npx playwright install chromium # once, if no browser is installed
Use in an MCP client
.mcp.json (Claude Code, Cursor, etc.):
{"mcpServers": {"playwright": {"command": "lite-locator-mcp", "args": ["--", "--headless", "--isolated"]}}}
Arguments after -- are passed to Playwright MCP. --lam sets the cut policy (0.002, 0.005, 0.01 or 0.02; a
higher value shows fewer candidates; the default is 0.01).
Environment variables:
PLAYWRIGHT_MCPoverrides the child command (defaultnpx -y @playwright/mcp@0.0.83).ELEM_RANK_LITEpoints to a different model bundle.
Build the wheel (from the repo)
.venv/bin/python -m elem_rank.export_onnx --out elem_rank/models-lite # ONNX int8 models, 57 MB
.venv/bin/python -m build # sdist + wheel in dist/
Credits and licences
- Code: MIT (see LICENSE).
- Retriever fine-tuned from BAAI/bge-small-en-v1.5 (MIT).
- Reranker fine-tuned from cross-encoder/ms-marco-MiniLM-L6-v2 (Apache-2.0).
- Training data includes Mind2Web (Deng et al., 2023, CC BY 4.0) and pages from public websites.
Metadata
Release files for lite-locator-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lite_locator_mcp-0.1.0.tar.gz | 38.2 MB | Without provenance | Details for lite_locator_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lite_locator_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lite_locator_mcp-0.1.0-py3-none-any.whl |
Total release size: 76.5 MB
Release files / lite_locator_mcp-0.1.0.tar.gz
| Download URL | lite_locator_mcp-0.1.0.tar.gz |
|---|---|
| Size | 38.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c9ffa85bc964a73907395e1a4fba405c1086151da13250bdd8cc93cbea89df8
|
|
BLAKE2b-256 checksum How to use checksums |
75fcb10d9d4c9f984b89cd692b2132078d290c43ec98d44cf7c154f4f9930e6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / lite_locator_mcp-0.1.0-py3-none-any.whl
| Download URL | lite_locator_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 38.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0eaf1d02fd6d7e1ce7b15ed9fa9d0e5764f48f7758c38a18d87ebc7be7aef490
|
|
BLAKE2b-256 checksum How to use checksums |
4523f290292c8557b3e4c4bb882f5c64613e698df8546fd75d441dd79eaf86ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for lite-locator-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.