Clickup · OAuth Scopes

Clickup OAuth Scopes

OAuth 2.0 searched

Clickup publishes 2 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Clickup API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Project ManagementWork ManagementProductivityCollaborationTaskDocumentsChatTime TrackingMCP

Scopes: 2 Flows: Method: searched

Scopes (2)

Scope	Description	Flows
read	Read access to the ClickUp MCP resource (tasks, documents, chat).	authorizationCode
write	Write access to the ClickUp MCP resource (tasks, documents, chat).	authorizationCode

📄 Provider scope reference: https://developer.clickup.com/docs/authentication

Source

OAuth Scopes

generated: '2026-09-17'
method: searched
source: >-
  https://developer.clickup.com/docs/authentication and
  well-known/clickup-mcp-oauth-authorization-server.json
docs: https://developer.clickup.com/docs/authentication
finding: >-
  The ClickUp public API OAuth flow has NO scope parameter and NO scope reference page. Authorization is
  granted per WORKSPACE, not per permission: the user picks which Workspaces an app may access, and the
  resulting token carries whatever that user can do. Neither published OpenAPI declares an oauth2
  securityScheme (both declare a single apiKey Authorization header), so derive-oauth-scopes.py has
  nothing to read — the absence is the contract, not a harvesting gap. The only scoped surface ClickUp
  operates is the MCP server, whose RFC 8414 metadata advertises two coarse scopes.
schemes:
- name: ClickUp OAuth 2.0 (public API)
  authorization_url: https://app.clickup.com/api
  token_url: https://api.clickup.com/api/v2/oauth/token
  grant_types: [authorization_code]
  scopes_supported: []
  authorization_unit: workspace
  note: Access tokens do not expire (documented in the developer FAQ).
- name: ClickUp MCP server
  source: https://mcp.clickup.com/.well-known/oauth-authorization-server
  authorization_url: https://mcp.clickup.com/oauth/authorize
  token_url: https://mcp.clickup.com/oauth/token
  registration_url: https://mcp.clickup.com/oauth/register
  grant_types: [authorization_code]
  code_challenge_methods: [S256]
scopes:
- scope: read
  description: Read access to the ClickUp MCP resource (tasks, documents, chat).
  flows: [authorizationCode]
  sources: [well-known/clickup-mcp-oauth-authorization-server.json, well-known/clickup-mcp-oauth-protected-resource.json]
  surface: mcp
- scope: write
  description: Write access to the ClickUp MCP resource (tasks, documents, chat).
  flows: [authorizationCode]
  sources: [well-known/clickup-mcp-oauth-authorization-server.json, well-known/clickup-mcp-oauth-protected-resource.json]
  surface: mcp

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/clickup-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.