A Personal API Token is the whole auth story, so the server acts as you and sees exactly what you see. One rough edge is flagged in the server itself: clickup_update_view runs into known issues on ClickUp's own v2 view endpoint, so if a view edit errors out, recreate the view instead of retrying.
An MCP server over the ClickUp API, authenticated with your own Personal API Token and run over stdio, exposing the workspace hierarchy as well as tasks.
- Tasks created and updated with status, priority, assignees, tags, due date, description and time estimate
- The workspace tree: teams, then spaces, folders and lists, each with create, read, update and delete
- Custom fields: list what is available on a list, then set or remove a value on a task
- Docs: search them across a workspace, create one, list its pages, read a page as Markdown, and edit page content or title
- Views: create list, board, calendar or gantt views on a team, space, folder or list, read a view's details, and pull the tasks inside it
- Board views created directly in a space
A ClickUp Personal API Token, generated under My Settings > Apps and supplied as CLICKUP_PERSONAL_TOKEN. That is the only required variable — LOG_LEVEL is optional, and PORT is not used in the default stdio mode. Launch it with npx @nazruden/clickup-server.
One command plus a key — npx @nazruden/clickup-server, then supply credentials