Hi! I'm trying to install SupaThings MCP on macOS but encountering a fatal memory error during the build step. Here's what's happening:
System:
macOS (latest)
Node.js v24.13.1
Installation path: ~/Desktop/SupaThings-MCP
Steps that succeed:
git clone https://github.com/soycanopa/SupaThings-MCP.git
cd SupaThings-MCP
npm install — completes successfully (94 packages, 0 vulnerabilities)
Step that fails:
4. npm run build — crashes with:
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
What happens:
The tsc command starts compiling
After ~57 seconds, Node.js runs out of memory and crashes
No build/ directory is created
Running npm run build again produces the same crash
What I've tried:
Multiple attempts — same crash every time
The crash is consistent and reproducible
Question:
Is there a known workaround for this? Should I:
Increase Node.js heap size manually? (If so, what's the recommended setting?)
Use a different Node.js version?
Is there a pre-built release I could use instead?
I'd really like to get this working — the SupaThings MCP would solve a significant data quality issue I'm experiencing with the current Things MCP (it's returning projects and headings mixed in with tasks in the Anytime view, making that view unusable).
Thanks for any guidance you can provide!
Hi! I'm trying to install SupaThings MCP on macOS but encountering a fatal memory error during the build step. Here's what's happening:
System:
macOS (latest)
Node.js v24.13.1
Installation path: ~/Desktop/SupaThings-MCP
Steps that succeed:
git clone https://github.com/soycanopa/SupaThings-MCP.git
cd SupaThings-MCP
npm install — completes successfully (94 packages, 0 vulnerabilities)
Step that fails:
4. npm run build — crashes with:
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
What happens:
The tsc command starts compiling
After ~57 seconds, Node.js runs out of memory and crashes
No build/ directory is created
Running npm run build again produces the same crash
What I've tried:
Multiple attempts — same crash every time
The crash is consistent and reproducible
Question:
Is there a known workaround for this? Should I:
Increase Node.js heap size manually? (If so, what's the recommended setting?)
Use a different Node.js version?
Is there a pre-built release I could use instead?
I'd really like to get this working — the SupaThings MCP would solve a significant data quality issue I'm experiencing with the current Things MCP (it's returning projects and headings mixed in with tasks in the Anytime view, making that view unusable).
Thanks for any guidance you can provide!