io.github.jmshinhwa/proto-wire-break-check MCP Server
io.github.jmshinhwa/proto-wire-break-check
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/proto-wire-break-check MCP server?
Names the .proto edits that keep compiling and quietly change what old gRPC readers see
How to install io.github.jmshinhwa/proto-wire-break-check
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"proto-wire-break-check": {
"command": "npx",
"args": [
"-y",
"@readystack/proto-wire-break-check",
"--mcp"
]
}
}
}Related MCP servers
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 →Prüft PHP-Rechnungstemplates von WooCommerce- und WordPress-Shops gegen alle zehn Pflichtangaben des
View repository →15 Checks für exportierte Reisekostenabrechnungen: 28,00 Euro Verpflegungspauschale erst ab 24 Stund
View repository →Find the .rpy lines that compile clean and only break inside a player's save
View repository →Checks robots.txt line by line and says what each AI crawler token actually controls - training, AI
View repository →