10aday › MCP tools
AI assistants often guess how git, npm, Node, Docker and browserslist read their config files, and guess wrong. Each server below computes the answer with the real rules, ported from the real tool and checked against it on tens of thousands of cases (0 differences). One click to install in Claude Desktop, VS Code or Cursor.
Exactly which browsers a browserslist query or config targets today, and whether a CSS/JS feature (:has(), container queries…) works in all of them. Real browserslist code and caniuse data.
Which file Node loads for import "pkg/sub" or require, which exports key decides, and the exact Node error when it fails.
Why a package is in node_modules, which versions, who pulls it in. Same answer as npm explain, read from package-lock.json.
Exactly which files npm publish ships, which rule decides each one, and leaks (.env, keys) to fix first.
Is this path ignored by git, and by which .gitignore line? Same answer as git check-ignore.
Which files docker build really sends, and which .dockerignore line decides. Exact BuildKit rules.
Which git attributes apply to a file (line endings, binary, LFS, linguist) and which line decides. Same as git check-attr.
Which .editorconfig settings apply to a file (indent, line endings, charset) and which section decides.
Which version a dependency constraint installs, in npm, Cargo, pip, Maven, Gradle, NuGet, Composer and RubyGems.