# How to connect Dropbox to Grok Bot (no API keys) > Connect Dropbox to Grok Bot with ClawLink in one click — 111 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/dropbox Grok Bot runs on its own cloud computer, so most Dropbox guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Dropbox setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Dropbox 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 dropbox` > 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 Dropbox. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Dropbox** — `npx -y @useclawlink/cli connect dropbox`, 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 dropbox # connect Dropbox (browser OAuth) npx -y @useclawlink/cli actions dropbox # list available actions npx -y @useclawlink/cli run dropbox --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 dropbox ``` 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: > Use Dropbox to copy file or folder and walk me through the result in plain English. ### 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 Dropbox is connected in the dashboard, that agent calls the same 111 Dropbox 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). ## Dropbox MCP for Grok Bot Looking for a Dropbox MCP server for Grok Bot? ClawLink connects Dropbox to Grok Bot and exposes 111 Dropbox 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 Dropbox integration](https://claw-link.dev/openclaw/dropbox) and the [Hermes Dropbox integration](https://claw-link.dev/hermes/dropbox) connect the same ClawLink account the same way. ## What the Grok Bot Dropbox integration can do 111 Dropbox 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 111. ### 30 of 111 Dropbox tools for Grok Bot | Tool | What it does | |---|---| | **Copy file or folder** `dropbox_copy_file_or_folder` | Copy a file or folder in Dropbox | | **Create folder** `dropbox_create_folder` | Create a new folder in Dropbox | | **Create shared link** `dropbox_create_shared_link` | Create a shared link for a Dropbox file or folder | | **Download zip** `dropbox_download_zip` | Download a Dropbox folder as a ZIP archive | | **Get metadata** `dropbox_get_metadata` | Get metadata for a Dropbox file or folder | | **Get space usage** `dropbox_get_space_usage` | Get current Dropbox storage space usage | | **Get temporary link** `dropbox_get_temporary_link` | Get a temporary link to download a Dropbox file | | **List file revisions** `dropbox_list_file_revisions` | List revisions of a Dropbox file | | **List folder continue** `dropbox_list_folder_continue` | List files and folders in a Dropbox folder | | **List shared links** `dropbox_list_shared_links` | List shared links in Dropbox | | **Move file or folder** `dropbox_move_file_or_folder` | Move a file or folder in Dropbox | | **Read file** `dropbox_read_file` | Read the contents of a Dropbox file | | **Search file or folder** `dropbox_search_file_or_folder` | Search Dropbox for files and folders | | **Share folder** `dropbox_share_folder` | Share a Dropbox folder with others | | **Upload file** `dropbox_upload_file` | Upload a file to Dropbox | | **Check copy batch** `dropbox_check_copy_batch` | Check the status of an asynchronous copy batch job in Dropbox | | **Check folder batch** `dropbox_check_folder_batch` | Check the status of an asynchronous folder batch creation job | | **Check job status** `dropbox_check_job_status` | Check the status of an asynchronous sharing job in Dropbox | | **Check move batch** `dropbox_check_move_batch` | Check the status of an asynchronous move batch job | | **Check save URL status** `dropbox_check_save_url_status` | Check the status of a save_url job in Dropbox | | **Check share job status** `dropbox_check_share_job_status` | Check the status of an asynchronous folder sharing job in Dropbox | | **Check upload batch** `dropbox_check_upload_batch` | Check the status of an asynchronous upload batch job in Dropbox | | **Check user** `dropbox_check_user` | Test Dropbox API connection and validate access token by echoing back a supplied string | | **Count file requests** `dropbox_count_file_requests` | Get the total number of file requests owned by the authenticated user | | **Export file** `dropbox_export_file` | Export non-downloadable Dropbox files (especially Dropbox Paper) to Markdown/HTML/plain text | | **Files search** `dropbox_files_search` | Search for files and folders in Dropbox by name or content | | **Get about me** `dropbox_get_about_me` | Get information about the current user's Dropbox account | | **Get account** `dropbox_get_account` | Get information about a user's Dropbox account using their account ID | | **Get account batch** `dropbox_get_account_batch` | Get information about multiple user accounts in a single request | | **Get copy reference** `dropbox_get_copy_reference` | Get a copy reference to a file or folder | ## Example prompts **Copy File Or Folder** > Use Dropbox to copy file or folder and walk me through the result in plain English. **Create Folder** > Create it in Dropbox for me, then confirm the important fields before you finish. **Create Shared Link** > Create it in Dropbox for me, then confirm the important fields before you finish. **Download Zip** > Use Dropbox to download zip and walk me through the result in plain English. ## 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 Dropbox working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Dropbox app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Dropbox 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 Dropbox. | 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 Dropbox actions to the runtime in a format your agent can reliably use. | 111 tools for Dropbox are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Dropbox 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 Dropbox in the browser, and the 111 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 Dropbox 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 Dropbox tools Dropbox 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 Dropbox 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. ### Dropbox 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 Dropbox 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 Dropbox integration? Yes. ClawLink is the fastest way to connect Grok Bot to Dropbox: link your Dropbox account once in the browser and Grok Bot can call the Dropbox API through 111 ready-made tools — no custom code or token handling. ### How do I connect Dropbox 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 dropbox` to authorize Dropbox. 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 Dropbox to Grok Bot? About two minutes. Sign in, click Connect next to Dropbox in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Dropbox 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 Dropbox 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 - [Grok Bot Box integration](https://claw-link.dev/grokbot/box) — Store, share, and manage files and folders - [Supabase](https://claw-link.dev/grokbot/supabase) — Query and manage Postgres databases - [Grok Bot Neon integration](https://claw-link.dev/grokbot/neon) — Serverless Postgres with branching and scale-to-zero