
Livewire3 Upgrade Blocker Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.3Updated Oct 24, 2026
The Livewire 2 lines that die quietly in Livewire 3 — named, with the v3 replacement beside each
Overview
A local lint helper that names Livewire 2 code patterns that break in Livewire 3 and shows the v3 replacement for each.
- What you can do
- This MCP server runs locally over stdio and is meant to surface Livewire 2 lines that fail silently after upgrading to Livewire 3. Its description says it names each problematic line and pairs it with the corresponding v3 replacement. The manifest lists no tools, so the exact commands an assistant can call are not documented here.
- When to use it
- Worth adding when you are migrating a Laravel project from Livewire 2 to Livewire 3 and want an assistant to point out code that would break quietly. It is a narrow, upgrade-specific helper rather than a general Laravel or PHP tool.
- Requirements
- Runs as a local process on the user's machine via npx from the npm package @readystack/livewire3-upgrade-blocker-lint, so Node.js and npm are needed. No authentication, environment variables, or headers are declared. Desktop only; no web executable.
Installation
In SourceWeft
- Open Livewire3 Upgrade Blocker Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.3LatestSep 23, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.