# How to connect ClickUp to Grok Bot (no API keys) > Connect ClickUp to Grok Bot with ClawLink in one click — 161 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/clickup Grok Bot runs on its own cloud computer, so most ClickUp guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical ClickUp setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real ClickUp actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect clickup` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to ClickUp. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect ClickUp** — `npx -y @useclawlink/cli connect clickup`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect clickup # connect ClickUp (browser OAuth) npx -y @useclawlink/cli actions clickup # list available actions npx -y @useclawlink/cli run clickup --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect clickup ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Create it in ClickUp for me, then confirm the important fields before you finish. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once ClickUp is connected in the dashboard, that agent calls the same 161 ClickUp tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## ClickUp MCP for Grok Bot Looking for a ClickUp MCP server for Grok Bot? ClawLink connects ClickUp to Grok Bot and exposes 161 ClickUp tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) and the [Hermes ClickUp integration](https://claw-link.dev/hermes/clickup) connect the same ClawLink account the same way. ## What the Grok Bot ClickUp integration can do 161 ClickUp tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 161. ### 30 of 161 ClickUp tools for Grok Bot | Tool | What it does | |---|---| | **Create checklist** `clickup_create_checklist` | Create a checklist in a ClickUp task | | **Create checklist item** `clickup_create_checklist_item` | Create an item in a ClickUp checklist | | **Create folder** `clickup_create_folder` | Create a new ClickUp folder | | **Create list** `clickup_create_list` | Create a new ClickUp list | | **Create list comment** `clickup_create_list_comment` | Add a comment to a ClickUp list | | **Create space** `clickup_create_space` | Create a new ClickUp space | | **Create task** `clickup_create_task` | Create a new ClickUp task | | **Create task comment** `clickup_create_task_comment` | Add a comment to a ClickUp task | | **Get folder** `clickup_get_folder` | Get a ClickUp folder by ID | | **Get folder views** `clickup_get_folder_views` | List ClickUp folder views | | **Get folders** `clickup_get_folders` | List ClickUp folders | | **Get list** `clickup_get_list` | Get a ClickUp list by ID | | **Get list comments** `clickup_get_list_comments` | List comments on a ClickUp list | | **Get list views** `clickup_get_list_views` | List ClickUp list views | | **Get lists** `clickup_get_lists` | List ClickUp lists | | **Get space** `clickup_get_space` | Get a ClickUp space by ID | | **Get space views** `clickup_get_space_views` | List ClickUp space views | | **Get spaces** `clickup_get_spaces` | List ClickUp spaces | | **Get task** `clickup_get_task` | Get a ClickUp task by ID | | **Get task comments** `clickup_get_task_comments` | List comments on a ClickUp task | | **Get task templates** `clickup_get_task_templates` | List ClickUp task templates | | **Get tasks** `clickup_get_tasks` | List ClickUp tasks with optional filters | | **Get view** `clickup_get_view` | Get a ClickUp view by ID | | **Get view tasks** `clickup_get_view_tasks` | List tasks from a ClickUp view | | **Start time entry** `clickup_start_time_entry` | Start a time entry for a ClickUp task | | **Stop time entry** `clickup_stop_time_entry` | Stop the current time entry in ClickUp | | **Update checklist** `clickup_update_checklist` | Update a ClickUp checklist | | **Update checklist item** `clickup_update_checklist_item` | Update a ClickUp checklist item | | **Update comment** `clickup_update_comment` | Update a ClickUp comment | | **Update folder** `clickup_update_folder` | Update a ClickUp folder | ## Example prompts **Create Checklist** > Create it in ClickUp for me, then confirm the important fields before you finish. **Create Checklist Item** > Create it in ClickUp for me, then confirm the important fields before you finish. **Create Folder** > Create it in ClickUp for me, then confirm the important fields before you finish. **Create List** > Create it in ClickUp for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want ClickUp working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a ClickUp app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect ClickUp through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for ClickUp. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right ClickUp actions to the runtime in a format your agent can reliably use. | 161 tools for ClickUp are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ClickUp to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect ClickUp in the browser, and the 161 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect ClickUp from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling ClickUp tools ClickUp tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every ClickUp call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### ClickUp returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting ClickUp and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot ClickUp integration? Yes. ClawLink is the fastest way to connect Grok Bot to ClickUp: link your ClickUp account once in the browser and Grok Bot can call the ClickUp API through 161 ready-made tools — no custom code or token handling. ### How do I connect ClickUp to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect clickup` to authorize ClickUp. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect ClickUp to Grok Bot? About two minutes. Sign in, click Connect next to ClickUp in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring ClickUp up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want ClickUp working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Trello](https://claw-link.dev/grokbot/trello) — Manage boards, lists, and cards - [Connect Moco](https://claw-link.dev/grokbot/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [Grok Bot Asana integration](https://claw-link.dev/grokbot/asana) — Track tasks, projects, and workflows