# CLICKUP_API_TOKEN environment variable is required (ClickUp MCP)

**TL;DR:** Set CLICKUP_API_TOKEN in the MCP server env block to your ClickUp personal API token. The server will not start without it; there is no interactive prompt. Restart the client after adding it.

## The error

```
CLICKUP_API_TOKEN environment variable is required
```

## Fix it

1. Generate a personal API token in ClickUp (avatar, Apps, API token).
   Expected: You have the token value.
2. Add CLICKUP_API_TOKEN with the token to the server env in your MCP config.
   Expected: The env block carries it.
3. Restart the MCP client.
   Expected: The server starts and tools list loads.

## When this applies

The ClickUp MCP server exits at startup naming the missing CLICKUP_API_TOKEN variable.

## When this does NOT apply

If the server starts but calls 401, the token value is wrong. Variable-name differences exist between forks; match your fork's README.

## Tool compatibility

taazkareem/clickup-mcp-server (also rocari/clickup-mcp variants)

## Also seen as

- ClickUp MCP missing API token
- CLICKUP_API_TOKEN not set
- ClickUp MCP will not start

## Why it happens

The server reads its credential only from the environment at startup. MCP clients do not prompt for missing env, so the server exits with this message instead of hanging.

## Edge cases

- Some forks use CLICKUP_API_KEY instead; check the README of your install.
- The team ID env (CLICKUP_TEAM_ID) is also needed for most tools.
- Rotate the token in ClickUp if it ever leaks; old ones keep working until revoked.