- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.7k
docs: Add troubleshooting guide for MCP ENAMETOOLONG error on macOS #8389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Add troubleshooting section for 'spawn ENAMETOOLONG' error on macOS - Include workaround using full command paths instead of PATH resolution - Reference related GitHub issues #7870 and #6699 - Update table of contents to include new section Generated with Continue (https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
| ✅ Review Complete Code Review Summary | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
| 🎉 This PR is included in version 1.31.0 🎉 The release is available on: Your semantic-release bot 📦🚀 | 
| 🎉 This PR is included in version 1.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 | 
| 🎉 This PR is included in version 1.28.0 🎉 The release is available on: Your semantic-release bot 📦🚀 | 
Summary
This PR adds documentation to help users work around the 'spawn ENAMETOOLONG' error that occurs when connecting to MCP servers on macOS.
Problem
When Continue spawns MCP server processes on macOS, it copies the entire process environment which can exceed system limits, causing an ENAMETOOLONG error. This particularly affects users with large development environments.
Solution
Document the workaround of using full command paths (e.g.,
/usr/local/bin/npx) instead of relying on PATH resolution.Changes
Related Issues
Testing
Notes
While this PR provides immediate help through documentation, a proper code fix is still needed to filter environment variables when spawning MCP processes. See the discussion in #7870 for implementation details.
Summary by cubic
Adds a troubleshooting guide for MCP server connection issues on macOS, documenting the "spawn ENAMETOOLONG" error caused by large environments when spawning MCP processes. Explains the workaround to use full command paths (e.g., /usr/local/bin/npx) instead of PATH, and links to related issues (#7870, #6699).