Bug: MCP does not find jiti in project

[Shinigami92]

Which packages are affected?

• @eslint/compat
• @eslint/config-array
• @eslint/config-helpers
• @eslint/core
• @eslint/mcp
• @eslint/migrate-config
• @eslint/object-schema
• @eslint/plugin-kit

Environment

Node version: 24.3.0
npm version: 11.4.2
pnpm version: 10.12.4
ESLint version: 9.30.1
Operating System: Windows 11

What did you do?

Added

{
	"servers": {
		"ESLint": {
			"type": "stdio",
			"command": "npx",
			"args": [
				"@eslint/mcp@latest"
			]
		}
	},
	"inputs": []
}

as user-configuration in VSCode

What did you expect to happen?

It works and tells me stuff

What actually happened?

Link to Minimal Reproducible Example

Participation

• I am willing to submit a pull request for this issue.

Additional comments

tested in https://github.com/faker-js/faker

[lumirlumir]

ping @eslint/eslint-tsc

[fasttime]

Thanks for the issue @Shinigami92. It seems that your project uses pnpm to build, whereas the MCP server is being started with the npx command in your config. Can you try to use pnpx instead?

{
	"servers": {
		"ESLint": {
			"type": "stdio",
-			"command": "npx",
+			"command": "pnpx",
			"args": [
				"@eslint/mcp@latest"
			]
		}
	},
	"inputs": []
}

[Shinigami92]

This results in

[nzakas]

When the MCP server is configured like this, it always downloads from npm, so just installing Jiti locally won't work because VS Code doesn't look there.

I think if you install globally first then it will work as it will cause VS Code to use the global version instead of downloading a new copy. Can you try this?

npm i @eslint/mcp jiti -g

[Shinigami92]

When the MCP server is configured like this, it always downloads from npm, so just installing Jiti locally won't work because VS Code doesn't look there.

I think if you install globally first then it will work as it will cause VS Code to use the global version instead of downloading a new copy. Can you try this?

npm i @eslint/mcp jiti -g

Run npm i @eslint/mcp jiti -g and now got this result:

[fasttime]

This results in

It looks like pnpx isn't always installed, but pnpm dlx should work the same way (reference). Can you try that?

-			"command": "npx",
+			"command": "pnpm dlx",

[Shinigami92]

This results in

It looks like pnpx isn't always installed, but pnpm dlx should work the same way (reference). Can you try that?

• 	"command": "npx",
  

• 	"command": "pnpm dlx",
  

Could it be that vscode mcp is running in some kind of sandbox?!

[fasttime]

Er... my bad. dlx should be an argument.

{
	"servers": {
		"ESLint": {
			"type": "stdio",
			"command": "pnpm",
			"args": [
				"dlx",
				"@eslint/mcp@latest"
			]
		}
	},
	"inputs": []
}

[Shinigami92]

Now I got this again