The set covers the whole file lifecycle, and the one destructive call is named safe_delete_item rather than delete. Setup is the cost: you register the Dropbox app yourself, choose its permission scopes, and complete an OAuth flow before the first call works. Refresh behaviour is tunable through the optional token variables.
A Dropbox integration server: twelve file and account tools over Dropbox's public API, authenticated with OAuth and PKCE. It is independent, not a Dropbox product.
- A folder listing, an account-wide search, and metadata for a single item (list_files, search_file_db, get_file_metadata)
- A file's contents read into the conversation, or downloaded to disk (get_file_content, download_file)
- Uploads, new folders, copies and moves (upload_file, create_folder, copy_item, move_item)
- A sharing link generated for an item (get_sharing_link)
- Deletion behind a safeguard rather than outright (safe_delete_item)
- The connected Dropbox account's details (get_account_info)
A Dropbox app you register in the App Console with scoped access and the permissions your calls need, plus a redirect URI pointing back at the server on your own machine. The environment carries that app's key and secret, the redirect URI, and a long passphrase of your own that encrypts the stored tokens. Built with npm run build, then npm run setup.