io.github.jmshinhwa/play-release-blocker-lint MCP Server
io.github.jmshinhwa/play-release-blocker-lint
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.jmshinhwa/play-release-blocker-lint MCP server?
Finds the lines that make Google Play reject your release - target API below 36, Billing Library bel
How to install io.github.jmshinhwa/play-release-blocker-lint
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"play-release-blocker-lint": {
"command": "npx",
"args": [
"-y",
"@readystack/play-release-blocker-lint",
"--mcp"
]
}
}
}Related MCP servers
12 rules read your CHANGELOG.md the way Directive (EU) 2024/2853 will read it from 2026-12-09: undat
View repository →Dates every quantum-vulnerable algorithm in your code against the NIST IR 8547 clock: deprecated aft
View repository →Checks PrivacyInfo.xcprivacy and your C#, Dart, JS, Swift and Kotlin source for Apple required-reaso
View repository →Names the .proto edits that keep compiling and quietly change what old gRPC readers see
View repository →19 date-aware checks on the [project] metadata that decides whether your next release uploads
View repository →Marks the lines in your test suite that current pytest no longer runs — and the config keys it silen
View repository →