Tailwind V4 Upgrade Blocker Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Oct 24, 2026

19 rules that find the Tailwind v3 syntax Tailwind v4 removed or silently redefined, in the file you

The publisher's own server: Tailwind App

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lints files for Tailwind v3 syntax removed or redefined in Tailwind v4, helping assistants flag upgrade blockers.

What you can do
Check a file for Tailwind v3 syntax that Tailwind v4 removed or silently redefined, using 19 lint rules. Report which parts of the file would block or change behavior in a v4 upgrade. Runs locally over stdio as an npm package started with npx.
When to use it
Useful when planning or reviewing a migration from Tailwind v3 to v4 and you want an assistant to point out deprecated or redefined utility syntax in your files before upgrading.
Requirements
Runs as a local process on the user's machine via npx from the npm package @readystack/tailwind-v4-upgrade-blocker-lint. Node.js and network access to fetch the package are needed. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The registry description is truncated and the README shows unrelated theme content, so the exact tool surface is unclear; verify behavior before relying on it. It reads the files you point it at, so avoid exposing sensitive source files.

Installation

In SourceWeft

  1. Open Tailwind V4 Upgrade Blocker Lint in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 19, 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.

Other Tailwind integrations