bug: VSCODE MCP Sampling failing due to a dependency. #115

New issue

Closed

opened 2025-10-14 15:42:35 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:42:35 -06:00

Owner

Originally created by @Jitha-afk on 9/10/2025

Description

Trying to use GHC license to run TM MCP, unable to start the MCP server, errors out with following:

2025-09-10 15:33:46.953 [info] Starting server taskmaster-ai
2025-09-10 15:33:46.954 [info] Connection state: Starting
2025-09-10 15:33:46.965 [info] Starting server from LocalProcess extension host
2025-09-10 15:33:47.045 [info] Connection state: Starting
2025-09-10 15:33:47.047 [info] Connection state: Running
2025-09-10 15:33:48.847 [warning] [server stderr] node:internal/modules/esm/resolve:275
2025-09-10 15:33:48.847 [warning] [server stderr]     throw new ERR_MODULE_NOT_FOUND(
2025-09-10 15:33:48.847 [warning] [server stderr]           ^
2025-09-10 15:33:48.848 [warning] [server stderr] 
2025-09-10 15:33:48.848 [warning] [server stderr] Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'C:\.tools\.npm\_npx\0726791833487271\node_modules\@ai-sdk\provider-utils\dist\index.mjs' imported from C:\.tools\.npm\_npx\0726791833487271\node_modules\ai\dist\index.mjs
2025-09-10 15:33:48.848 [warning] [server stderr]     at finalizeResolution (node:internal/modules/esm/resolve:275:11)
2025-09-10 15:33:48.848 [warning] [server stderr]     at moduleResolve (node:internal/modules/esm/resolve:860:10)
2025-09-10 15:33:48.848 [warning] [server stderr]     at defaultResolve (node:internal/modules/esm/resolve:984:11)
2025-09-10 15:33:48.849 [warning] [server stderr]     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12)
2025-09-10 15:33:48.849 [warning] [server stderr]     at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25)
2025-09-10 15:33:48.849 [warning] [server stderr]     at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38)
2025-09-10 15:33:48.849 [warning] [server stderr]     at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38)
2025-09-10 15:33:48.849 [warning] [server stderr]     at ModuleJob._link (node:internal/modules/esm/module_job:137:49) {
2025-09-10 15:33:48.849 [warning] [server stderr]   code: 'ERR_MODULE_NOT_FOUND',
2025-09-10 15:33:48.850 [warning] [server stderr]   url: 'file:///C:/.tools/.npm/_npx/0726791833487271/node_modules/@ai-sdk/provider-utils/dist/index.mjs'
2025-09-10 15:33:48.850 [warning] [server stderr] }
2025-09-10 15:33:48.850 [warning] [server stderr] 
2025-09-10 15:33:48.850 [warning] [server stderr] Node.js v22.16.0
2025-09-10 15:33:48.884 [info] Connection state: Error Process exited with code 1
2025-09-10 15:33:48.885 [error] Server exited before responding to `initialize` request.

Steps to Reproduce

Fresh install MCP using the following config

"taskmaster-ai":{
			"command":"npx",
			"args":["-y", "--package=task-master-ai", "task-master-ai"],
			"type":"stdio"
		},

"chat.mcp.serverSampling": {
        "Global in Code: taskmaster-ai": {
            "allowedModels": [
                "copilot/gpt-4.1",
                "copilot/claude-opus-4",
                "copilot/claude-opus-41",
                "copilot/claude-sonnet-4",
                "copilot/gemini-2.5-pro",
                "copilot/gpt-4o",
                "copilot/gpt-5",
                "copilot/gpt-5-mini"
            ]
        }
    },

Enabled sampling in VSC for the MCP server.
Start the MCP server and it fails with above error.

Expected Behavior

MCP server is able to start.

Actual Behavior

MCP server fails to start, which leads to agent mode unable to find tools.

Environment

Task Master version: latest 0.26
Node.js version: 22.16
Operating system: Win11
IDE (if applicable): VSCODE

*Originally created by @Jitha-afk on 9/10/2025* ### Description Trying to use GHC license to run TM MCP, unable to start the MCP server, errors out with following: ``` 2025-09-10 15:33:46.953 [info] Starting server taskmaster-ai 2025-09-10 15:33:46.954 [info] Connection state: Starting 2025-09-10 15:33:46.965 [info] Starting server from LocalProcess extension host 2025-09-10 15:33:47.045 [info] Connection state: Starting 2025-09-10 15:33:47.047 [info] Connection state: Running 2025-09-10 15:33:48.847 [warning] [server stderr] node:internal/modules/esm/resolve:275 2025-09-10 15:33:48.847 [warning] [server stderr] throw new ERR_MODULE_NOT_FOUND( 2025-09-10 15:33:48.847 [warning] [server stderr] ^ 2025-09-10 15:33:48.848 [warning] [server stderr] 2025-09-10 15:33:48.848 [warning] [server stderr] Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'C:\.tools\.npm\_npx\0726791833487271\node_modules\@ai-sdk\provider-utils\dist\index.mjs' imported from C:\.tools\.npm\_npx\0726791833487271\node_modules\ai\dist\index.mjs 2025-09-10 15:33:48.848 [warning] [server stderr] at finalizeResolution (node:internal/modules/esm/resolve:275:11) 2025-09-10 15:33:48.848 [warning] [server stderr] at moduleResolve (node:internal/modules/esm/resolve:860:10) 2025-09-10 15:33:48.848 [warning] [server stderr] at defaultResolve (node:internal/modules/esm/resolve:984:11) 2025-09-10 15:33:48.849 [warning] [server stderr] at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12) 2025-09-10 15:33:48.849 [warning] [server stderr] at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25) 2025-09-10 15:33:48.849 [warning] [server stderr] at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38) 2025-09-10 15:33:48.849 [warning] [server stderr] at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38) 2025-09-10 15:33:48.849 [warning] [server stderr] at ModuleJob._link (node:internal/modules/esm/module_job:137:49) { 2025-09-10 15:33:48.849 [warning] [server stderr] code: 'ERR_MODULE_NOT_FOUND', 2025-09-10 15:33:48.850 [warning] [server stderr] url: 'file:///C:/.tools/.npm/_npx/0726791833487271/node_modules/@ai-sdk/provider-utils/dist/index.mjs' 2025-09-10 15:33:48.850 [warning] [server stderr] } 2025-09-10 15:33:48.850 [warning] [server stderr] 2025-09-10 15:33:48.850 [warning] [server stderr] Node.js v22.16.0 2025-09-10 15:33:48.884 [info] Connection state: Error Process exited with code 1 2025-09-10 15:33:48.885 [error] Server exited before responding to `initialize` request. ``` ### Steps to Reproduce 1. Fresh install MCP using the following config ```json "taskmaster-ai":{ "command":"npx", "args":["-y", "--package=task-master-ai", "task-master-ai"], "type":"stdio" }, "chat.mcp.serverSampling": { "Global in Code: taskmaster-ai": { "allowedModels": [ "copilot/gpt-4.1", "copilot/claude-opus-4", "copilot/claude-opus-41", "copilot/claude-sonnet-4", "copilot/gemini-2.5-pro", "copilot/gpt-4o", "copilot/gpt-5", "copilot/gpt-5-mini" ] } }, ``` 2. Enabled sampling in VSC for the MCP server. 3. Start the MCP server and it fails with above error. ### Expected Behavior MCP server is able to start. ### Actual Behavior MCP server fails to start, which leads to agent mode unable to find tools. ### Environment - Task Master version: latest 0.26 - Node.js version: 22.16 - Operating system: Win11 - IDE (if applicable): VSCODE