Dropbox
Connect AI agents and workflows to Dropbox: upload, download, move and share files, restore revisions, collect files with file requests, and act on new files.
Book a demoDropbox for AI agents and workflows.
engini lets your AI agents and workflows work in Dropbox: upload, download, copy, move, rename and delete files and folders, restore earlier revisions, create and manage share links, and collect files from people outside the company with file requests, with a trigger on new files. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Dropbox. Every tool is one you allow or leave out.
The Dropbox tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Find and read files.
Read a file's history.
Read file requests.
Write
Write files.
Organize.
Bring back an earlier revision.
Share.
Ask someone outside for files.
Delete
Remove files, links and old requests.
Any endpoint
Call any Dropbox API endpoint, with the sign-in added for you.
Triggers
New files in the folder you choose.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Dropbox. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Dropbox connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Dropbox tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Dropbox and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Dropbox tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Dropbox through engini
{
"mcpServers": {
"engini-dropbox": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Dropbox connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Dropbox tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Dropbox. Agents and workflows, across systems.
Vendor documents, collected
A file request collects W-9s and invoices from vendors, and new files are entered in the ERP.
Contracts shared on close
When a deal closes, share the signed contract with the customer and attach the link to the account.
New files that start work
A new file in a folder starts a workflow that reads it and files it.
Find the right file
An agent in Claude searches folders and answers from the files. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Dropbox and another system engini connects is available.
You decide what each agent may do in Dropbox. engini enforces it on every call.
Only the tools you allow
A toolset lists the Dropbox tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Dropbox account and engini acts as that person, with their Dropbox permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Dropbox in three steps. Then decide what each agent may do.
Sign in to Dropbox
Add a Dropbox connection and sign in through engini, or use your own Dropbox app.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Dropbox from Claude, ChatGPT, Cursor or your own code.
Dropbox and engini. Straight answers.
Can an AI agent write to Dropbox, or only read?
Both. engini has tools to upload, copy, move, rename, restore and delete files and folders, share them and manage file requests. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Dropbox?
It acts as the Dropbox account behind the connection, with that account's access. Every run is recorded under the person who started it.
Can a change in Dropbox start work?
Yes. A scheduled trigger checks for new files in the folder you choose. The workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Dropbox API endpoint through the same connection, and give it only to the agents that need it.