ClickUp

The ClickUp connector uses ClickUp’s Model Context Protocol (MCP) server to provide live, permission-aware access to your work management data. Instead of using a crawler or maintaining an indexed corpus, Glean Search, Assistant, and agents query ClickUp content directly.

​

Supported features

• Real-time data access: This live-mode MCP connector queries ClickUp directly, providing the most up-to-date results without the need for crawl schedules or index management. Because results are fetched at request time, they always reflect the current state of your ClickUp workspace.
• Federated search & fetch: Glean executes live searches against the ClickUp MCP server to retrieve tasks, docs, and other assets. When deep context is required—such as for Glean Assistant answers or rich previews—Glean fetches full task details, including comments and document page content, on demand.
• Core module coverage: The connector is optimized for ClickUp’s primary work management objects, providing deep support for the hierarchy of Spaces, Folders, and Lists, as well as Tasks and Docs.

​

Supported objects

The connector focuses on core ClickUp work management objects and exposes them through live (federated) queries:

• Tasks (including standard task fields and custom fields).
• ClickUp Docs (multi‑page documents with rich text content).
• Additional asset types that may appear in results when available through the MCP server, such as whiteboards, dashboards, attachments, and chat messages.

​

Scope

The ClickUp connector returns tasks and docs from the ClickUp workspaces that users have authorized in Glean, along with key metadata that helps users interpret search results.

​

Tasks

Task results can include task content, comments, and available metadata. In Glean, task results surface a clear title, a snippet from the description or comments, and key metadata such as status, assignees, list and space, priority, due date, and last updated time.

​

Docs

Doc results can include document content and available metadata. In Glean, doc results surface a title, a content snippet, and key metadata such as owner, location, and last updated time.

​

Use case examples

The ClickUp connector enables leaders in Product, Engineering, PMO, and Customer Success to access real-time project data. Here are examples of how different teams can query ClickUp directly from Glean:

• Project & program management
  • “Find all tasks related to the ‘Q4 Marketing Launch’.”
  • “Show my team’s tasks due this week and summarize their current status.”
  • “Summarize the latest progress on Feature Y based on task descriptions and comments.”
• Engineering & incident response
  • “Find all tasks related to Incident X across all product spaces.”
  • “Show me all tasks assigned to Jane Doe that are currently in progress.”
  • “What is the status of the tasks blocked this week in the Development folder?”
• Knowledge & operations
  • “Summarize the ‘Onboarding’ page from the ‘Team Wiki’ Doc.”
  • “Find all tasks in the Roadmap space that were updated in the last 7 days.”
  • “Who is currently part of the Engineering team in ClickUp?”

​

Requirements

​

Technical requirements

To use the ClickUp connector, you need:

• Access to the Glean Admin Console with permission to add and configure data sources.
• 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 the 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.

​

Setup and configuration

​

Step 1: Admin setup in Glean

1. In the Glean Admin Console, go to Data sources > Add data source and select ClickUp.
2. Enter a Name and optional Icon. This label appears to users in search results and configuration views.
3. Click Save. This stores the ClickUp MCP server configuration for your deployment using the built‑in ClickUp MCP server URL and metadata.
4. 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:

1. When a user first triggers a ClickUp action (for example, by running a search or Assistant query that needs ClickUp data), Glean initiates the ClickUp OAuth flow for that user.
2. The user signs in to ClickUp (if not already signed in) and approves access for the requested workspace(s).
3. 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.

​

Permissions & security

​

Permission model

The connector mirrors ClickUp’s workspace‑based authorization model as exposed via MCP:

• During OAuth, users grant access for specific ClickUp workspaces; the MCP server then enforces what objects each user can see based on their ClickUp role and membership in those workspaces.
• Glean issues all MCP calls using the current user’s token, so results are permission‑aware: users cannot see ClickUp tasks or docs they would not be able to access directly in ClickUp.

​

Data access model

• All ClickUp data is retrieved on demand via the ClickUp MCP server URL https://mcp.clickup.com/mcp using the STREAMABLE_HTTP transport.
• The connector is designed as a live‑mode integration and does not maintain a separate ClickUp index or document processor in Glean; ClickUp appears in Search, Assistant, and agents via federated search/fetch, not via a crawler.

Glean’s standard platform‑level security (encryption in transit and at rest, tenant isolation, and audit logging) continues to apply to any transient ClickUp content used to answer queries.

​

Troubleshooting

​

Connectivity and setup issues

If the Save or Authorize action fails while configuring ClickUp in the Admin Console:

• Verify account access: Ensure you are completing the OAuth flow with a ClickUp account that has permissions for the intended workspace(s).

If problems persist, capture the error message and contact Glean Support with your ClickUp workspace ID and connector configuration details.

​

Missing ClickUp results

If users cannot find ClickUp tasks or docs they expect to see:

• Check User Authentication: Confirm the user has completed their own ClickUp OAuth flow within Glean. Because MCP connectors use per-user OAuth, Glean cannot query ClickUp on a user’s behalf until they authenticate.
• Verify ClickUp Permissions: Ensure the user has direct access to the relevant workspaces, folders, or tasks within ClickUp. The connector only returns records that ClickUp’s APIs expose for that specific user’s token.
• Refresh the connection: If access roles were recently changed in ClickUp, the user may need to re-authenticate. The connector will automatically prompt for a new OAuth flow if it encounters a “401 Unauthorized” or “403 Forbidden” response.

​

Broad or incomplete search results

If search results are too broad or difficult to navigate, use a more specific query that includes:

• Task or document titles
• Assignee names
• Workspace context

​

FAQs