ClickUp hosted MCP client
Confirm the user and available ClickUp workspaces before selecting a team for reporting.
ConnectorConnect the hosted client
Node.js22+. The first run is an offline plan. Real discovery and execution use your PIPMCP_API_KEY; provider credentials stay in PipMCP.
git clone https://github.com/jannikco/clickup-mcp.git
cd clickup-mcp
npm ci --ignore-scripts
npm test
npm start
# Set PIPMCP_API_KEY in your environment
npm run doctor
# Launch from an MCP client as a stdio command
npm run serverOne PipMCP key, hosted provider access
Create an account key with connectors:read for discovery and connectors:call for calls. Set PIPMCP_API_KEY in the client environment. Connect the authorized provider account in PipMCP.
When multiple accounts are available, choose explicit PIPMCP_INTEGRATION_ID and PIPMCP_CONNECTION_ID from the hosted inventory. A missing app, missing connection and insufficient scope are different account conditions.
Discover the tools your account can use
This package reads the actual published tool names and schemas from PipMCP. It does not bundle provider HTTP routes, credential mappings or execution plans.
The connector executes through the private hosted gateway. The selected account and live inventory define which operations are callable.
node lib/cli.mjs doctor --connector clickupOrdinary MCP tool calls go through hosted permissions and confirmation policy. A pending confirmation must be reviewed in PipMCP; the bridge never approves it. A subsequent explicit call resumes that same confirmation with its original key. Uncertain writes remain held.
Workspace access review
Confirm the user and available ClickUp workspaces before selecting a team for reporting.
What the evidence establishes
| Capability | Level | Scope |
|---|---|---|
| Client transport and stdio | Tested | Fixtures test the client contract; no provider outcome is implied. |
| Current hosted provider execution | Documented | No current provider Live outcome is established by this directory. |
Tool discovery is not provider execution. Pending, confirmation-required, uncertain, failed and succeeded receipts remain distinct. Inspect returned data before claiming final delivery.