Environment Variables Not Recognized (clickupApiKey, clickupTeamId) Despite Being Set

[Nux-Game]

Hi team,

I’m trying to run the clickup-mcp-server locally on Windows 10 with Node.js v22.14.0, but I consistently encounter this error:

Error: Missing required environment variables: clickupApiKey, clickupTeamId
What I've tried so far:
Set environment variables in PowerShell:

$env:clickupApiKey="pk_*****B3VQ1N"
$env:clickupTeamId="2420220"
node build/server.js

Set environment variables in Command Prompt:

set clickupApiKey=pk_*****B3VQ1N
set clickupTeamId=2420220
node build/server.js

Used a .env file with dotenv-cli:

clickupApiKey=pk_*****B3VQ1N
clickupTeamId=2420220

Ran:

dotenv -- node build/server.js
Verified environment variables are set correctly:

node -e "console.log(process.env.clickupApiKey, process.env.clickupTeamId)" This outputs the expected values.

Tried renaming environment variables to uppercase (CLICKUPAPIKEY, CLICKUPTEAMID) and mapped them to lowercase in the session, but the application still didn’t pick them up:

$env:CLICKUPAPIKEY=$env:clickupApiKey
$env:CLICKUPTEAMID=$env:clickupTeamId
node build/server.j
```s
Despite all of the above, the application still reports the variables as missing.


Is there a specific format, capitalization, or source required for these environment variables to be recognized?
Does the application expect them to come exclusively from a .env file or Docker environment?
Are there any known Windows-specific quirks in how this project handles environment variables?
Appreciate any insights or guidance on this issue!


































































Hi team,

I’m trying to run the clickup-mcp-server locally on Windows 10 with Node.js v22.14.0, but I consistently encounter this error:

javascript
Copy
Edit
Error: Missing required environment variables: clickupApiKey, clickupTeamId
What I've tried so far:
Set environment variables in PowerShell:

powershell
Copy
Edit
$env:clickupApiKey="pk_*****B3VQ1N"
$env:clickupTeamId="2420220"
node build/server.js
Set environment variables in Command Prompt:

cmd
Copy
Edit
set clickupApiKey=pk_*****B3VQ1N
set clickupTeamId=2420220
node build/server.js
Used a .env file with dotenv-cli:

ini
Copy
Edit
clickupApiKey=pk_*****B3VQ1N
clickupTeamId=2420220
Ran:

bash
Copy
Edit
dotenv -- node build/server.js
Verified environment variables are set correctly:

bash
Copy
Edit
node -e "console.log(process.env.clickupApiKey, process.env.clickupTeamId)"
This outputs the expected values.

Tried renaming environment variables to uppercase (CLICKUPAPIKEY, CLICKUPTEAMID) and mapped them to lowercase in the session, but the application still didn’t pick them up:

powershell
Copy
Edit
$env:CLICKUPAPIKEY=$env:clickupApiKey
$env:CLICKUPTEAMID=$env:clickupTeamId
node build/server.js
Despite all of the above, the application still reports the variables as missing.

Request:
Is there a specific format, capitalization, or source required for these environment variables to be recognized?

Does the application expect them to come exclusively from a .env file or Docker environment?

Are there any known Windows-specific quirks in how this project handles environment variables?

Appreciate any insights or guidance on this issue!