401 from ClickUp API through the MCP server

401 from ClickUp API through the MCP server

TL;DR: Regenerate your ClickUp personal API token; the current one is invalid, expired, or revoked. Update CLICKUPAPITOKEN in the MCP config and restart the client. Test the token with a direct ClickUp API call to confirm before blaming the server.

The error

401 from ClickUp API

Fix it

1. Call the ClickUp API directly with your token (e.g. list authorized teams).

Expected: It 401s, proving the token is the problem.

1. Generate a new personal API token in ClickUp.

Expected: You have the new value.

1. Update CLICKUPAPITOKEN in the MCP config and restart the client.

Expected: Tool calls succeed.

When this applies

ClickUp MCP starts normally but every API call returns 401.

When this does NOT apply

Startup failures naming the variable are the missing-env issue. Schema errors block tools from loading at all.

Tool compatibility

taazkareem/clickup-mcp-server, any version

Also seen as

• ClickUp MCP unauthorized
• ClickUp API token invalid MCP
• ClickUp MCP 401 every call

Why it happens

ClickUp invalidates tokens on regeneration, expiry, or revocation. The MCP server forwards the stored token verbatim, so a dead token 401s every call while the server itself looks healthy.

Edge cases

• ClickUp shows token creation dates; check for expiry.
• Workspace guests lose API access when removed; their tokens 401.
• The remote hosted server uses a license key plus token; check both.