MCP server that grounds coding agents on the dependency versions ACTUALLY installed in the current project — read from the lockfile and node_modules
Connect Installed to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server that grounds coding agents on the dependency versions ACTUALLY installed in the current project — read from the lockfile and node_modules — so they stop coding against a blend of every version. The installed mcp server is what makes that connection.
An MCP server that tells Claude, Cursor, and any MCP client the exact version of each dependency installed in the current project — read from node_modules and the lockfile, fully offline. Studies put AI-generated deprecated-API usage at 25–38%; the root cause is that the model doesn't know which version is on disk. This fixes that.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
installed_version — Exact installed version of one package (from node_modules, else lockfile) + declared range + drift vs npm latestresolve_imports — Pass the packages you're about to import; get each one's installed version in a single grounding callproject_versions — Every dependency's installed version from the lockfile — whole tree or direct-only, with a substring filterConfiguration is passed through the environment: INSTALLED_VERSION_PROJECT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at installed-version-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Installed's toolset — installed_version, resolve_imports, project_versions — is a fair guide to whether it matches your workflow. It is maintained by anicodeth; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Installed's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| installed_version | Exact installed version of one package (from node_modules, else lockfile) + declared range + drift vs npm latest. |
| resolve_imports | Pass the packages you're about to import; get each one's installed version in a single grounding call. |
| project_versions | Every dependency's installed version from the lockfile — whole tree or direct-only, with a substring filter. |
{
"mcpServers": {
"installed-version": {
"command": "npx",
"args": ["-y", "installed-version-mcp"],
"env": { "INSTALLED_VERSION_PROJECT": "/abs/path/to/your/project" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| INSTALLED_VERSION_PROJECT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.