# ClickUp setup for PopMCP

You paste one value into PopMCP: your ClickUp Personal API Token, a single string beginning with pk_.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.clickup.com/api/v2
- Credentials screen: https://app.clickup.com/settings/apps
- Provider docs: https://developer.clickup.com/docs/authentication

## Before you begin

- Any ClickUp account, including Free Forever
- Membership of every Workspace you want the MCP to reach. A personal token carries your own access and nothing more.
- No admin role required. Anyone with a ClickUp login can generate a personal token.

## Get your credentials

### 1. Open your personal settings

Sign in at app.clickup.com and click your avatar in the top-right corner. Choose Settings.

Screen: https://app.clickup.com/settings/profile

### 2. Open Apps in the settings sidebar

Under My Settings in the sidebar, click Apps. The API Token block sits at the top of the page.

Screen: https://app.clickup.com/settings/apps

### 3. Generate and copy the token

Click Generate, or Regenerate if a token already exists. Click Copy to put the `pk_` value on your clipboard.

Screen: https://app.clickup.com/settings/apps

### 4. Paste the token into PopMCP

In PopMCP, paste the value into API token and click Save.

## Fields PopMCP asks for

- API token (apiToken) [required]: In ClickUp, open your avatar (top-right) → Settings → Apps → API Token, then Generate (or copy) your Personal API Token. It starts with pk_. An OAuth2 access token works here too. Stored encrypted; used server-side only.

## Verify

PopMCP shows the ClickUp connection as Connected and the workspace picker fills with the ClickUp Workspaces your account belongs to.

## Troubleshooting

### There is no API Token block on the settings page

Cause: You opened Workspace settings from the Workspace avatar in the top-left. The personal token lives in your own settings.

Fix: Open **Settings** from your avatar in the top-right, then click **Apps** in the sidebar.

### 401 with `Token not found` or `OAUTH_017`

Cause: The token was pasted with a `Bearer ` prefix, or truncated when copied.

Fix: Re-copy with the **Copy** button and paste the raw value. It must start with `pk_` and contain no spaces. ClickUp expects the raw token in the `Authorization` header with no prefix, which PopMCP handles.

### `Team not authorized` on some Spaces or Lists

Cause: Personal tokens only reach Workspaces your own user is a member of.

Fix: Have a Workspace owner invite your user, or generate the token from an account that already has access.

### 429 Too Many Requests

Cause: You crossed the per-token per-minute rate limit for your plan.

Fix: Wait for the window in the `X-RateLimit-Reset` header and reduce polling frequency in your automations.

### The token stopped working overnight

Cause: Somebody clicked **Regenerate**, which invalidates the previous token instantly.

Fix: Generate a fresh token and paste the new value into PopMCP.

---

Source: https://www.docs.popmcp.com/docs/integrations/clickup/