io.github.jmshinhwa/config-dsl-lint-snippet-pack MCP Server
io.github.jmshinhwa/config-dsl-lint-snippet-pack
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/config-dsl-lint-snippet-pack MCP server?
Your config files are never compiled — nothing fails until deploy. 36 snippets and 28 lint rules for
How to install io.github.jmshinhwa/config-dsl-lint-snippet-pack
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"config-dsl-lint-snippet-pack": {
"command": "npx",
"args": [
"-y",
"@readystack/config-dsl-lint-snippet-pack",
"--mcp"
]
}
}
}Related MCP servers
26 rules and 32 safe-replacement snippets for hardcoded connection strings, keys and kubeconfigs acr
View repository →Finds the analytics, pixels, fonts and embeds that fire before your cookie banner is answered - in t
View repository →Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo
View repository →Reads a Dockerfile or compose file and names the hardening controls it fails, with the NIST SP 800-1
View repository →Finds the coverage gates in your repo that can never fail a build
View repository →Reads your SECURITY.md against the EU Cyber Resilience Act reporting clock that started on 11 Septem
View repository →