# Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server/stdio.js' is not defined by "exports" (ClickUp MCP)

**TL;DR:** Upgrade Node.js to v18 or higher; the MCP SDK needs modern ESM export resolution. The error means your Node is too old (e.g. v12) to resolve the SDK package exports. Clear the npm cache after upgrading, then restart the client.

## The error

```
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server/stdio.js' is not defined by "exports"
```

## Fix it

1. Run node --version.
   Expected: It shows v12 or another version below v18.
2. Install Node 20 LTS (via nvm or nodejs.org).
   Expected: node --version now shows v20.
3. Run npm cache clean --force.
   Expected: The cache clears.
4. Restart the MCP client.
   Expected: The ClickUp server starts without the exports error.

## When this applies

The ClickUp MCP server fails at startup with the ERR_PACKAGE_PATH_NOT_EXPORTED error naming server/stdio.js.

## When this does NOT apply

If the server starts but tools fail, that is auth or schema. If Node is already v18+, the install is corrupt; reinstall.

## Tool compatibility

taazkareem/clickup-mcp-server, Node.js below v18

## Also seen as

- ClickUp MCP node version error
- stdio.js not exported ClickUp
- ClickUp MCP requires node 18

## Why it happens

The @modelcontextprotocol/sdk package uses modern ES module exports that Node 12 cannot resolve. The old resolver throws instead of loading the server entrypoint.

## Edge cases

- nvm lets you switch per-shell; make sure the MCP client inherits the new Node.
- The -y flag behavior also differs on old npm; the upgrade fixes both.
- Docker users should bump the base image tag.