Before submitting your bug report
- I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
- I believe this is a bug. I'll try to join the Continue Discord for questions
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS:macOS - Continue version:1.3.11 - IDE version:VSCode 1.104.0 - Node:v22.19.0 - config: name: Memory MCP server version: 0.0.1 schema: v1 mcpServers: - name: Memory MCP server command: npx args: - -y - "@modelcontextprotocol/server-memory"
Description
Node was installed using the official nvm method: https://nodejs.org/zh-cn/download
After configuring the MCP file, it can be started from the shell, and the service can also be used from a remote URL.
Only the npx method fails to start, and the error message appears:
Failed to connect to "Memory MCP server"
Error: spawn ENAMETOOLONG
I run npx normally in the local command line:
>npx -v
10.9.3
To reproduce
No response
Log output
Opening the VSCode console, I see the following error: console.ts:137 [Extension Host] Failed to fetch MCP prompt content for write_custom_semgrep_rule from server Semgrep MCP: McpError: MCP error 0: Missing required arguments: {'code', 'language'} at Client2._onresponse (/Users/666/.vscode/extensions/continue.continue-1.3.11/out/extension.js:259662:26) at _transport.onmessage (/Users/666/.vscode/extensions/continue.continue-1.3.11/out/extension.js:259542:18) at StreamableHTTPClientTransport.send (/Users/666/.vscode/extensions/continue.continue-1.3.11/out/extension.js:267370:79) at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
