ClickUp setup
Requirements
Technical requirements
To use the ClickUp connector, you need:
- Access to Glean Admin Console with permission to add and configure connectors.
- A ClickUp workspace whose users can complete an OAuth 2.0 with DCR flow against the ClickUp MCP server, authorizing Glean’s MCP client for that workspace.
Credential requirements
The connector uses OAuth tokens obtained from ClickUp rather than long‑lived admin passwords or API tokens:
- Admin‑level OAuth: A Glean admin initiates OAuth against the ClickUp MCP server from Glean Admin Console during setup, establishing the MCP server configuration for the deployment.
- Per‑user OAuth: Each end user authenticates individually with ClickUp via OAuth; the connector uses those per‑user tokens for all MCP calls on that user’s behalf.
Step 1: Admin setup in Glean
- In the Glean Admin Console, go to Connectors → Add connector and select ClickUp.
- Enter a Name and optional Icon. This label appears to users in search results and configuration views.
- Click Save. This stores the ClickUp MCP server configuration for your deployment using the built‑in ClickUp MCP server URL and metadata.
- After saving, click Authorize and complete the ClickUp OAuth flow in the popup window using an account that has access to the relevant ClickUp workspace(s).
After the admin completes this flow successfully, the ClickUp MCP server is registered for your Glean deployment, and the connector is ready for end‑user authorization and use.
Step 2: End‑user authorization
Because the connector relies on per‑user OAuth, each user who wants to use ClickUp data in Glean must authorize ClickUp for their own account:
- When a user first triggers a ClickUp tool (for example, by running a search or Glean query that needs ClickUp data), Glean initiates the ClickUp OAuth flow for that user.
- The user signs in to ClickUp (if not already signed in) and approves access for the requested workspace(s).
- Glean stores the resulting OAuth token in its encrypted per‑user token store and uses it for subsequent MCP calls until it expires or is revoked, at which point Glean prompts the user to re‑authenticate.