About Dropbox
Dropbox is an MCP server that wraps Dropbox API v2 for browsing, searching and managing files and folders. It lets users inspect metadata, retrieve file contents and create folders through gateway or local stdio access.
Key features
- 01List folder contents
- 02Search files and folders
- 03Inspect file and folder metadata
- 04Download file contents
- 05Create folders
Use cases
- 01Locate a file by name or content
- 02Review file details before processing
- 03Retrieve documents for inspection
- 04Organize files into new folders
MCP support
Exposes Dropbox folder listing, search, metadata, download and folder creation tools to MCP clients. It runs locally over stdio or through the Pipeworx gateway.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/dropbox/mcpclaude mcp add --transport http pipeworx-io-dropbox https://gateway.pipeworx.io/dropbox/mcp{"mcpServers":{"pipeworx-io-dropbox":{"type":"http","url":"https://gateway.pipeworx.io/dropbox/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-dropbox":{"type":"http","url":"https://gateway.pipeworx.io/dropbox/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-dropbox":{"type":"http","url":"https://gateway.pipeworx.io/dropbox/mcp"}}}{"mcpServers":{"pipeworx-io-dropbox":{"serverUrl":"https://gateway.pipeworx.io/dropbox/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-dropbox
Dropbox MCP Pack — wraps the Dropbox API v2
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
dropbox_list_folder | List files and folders in a Dropbox directory. Returns names, types, sizes, and modification dates. Use when browsing folder contents or checking what's stored at a path. |
dropbox_search | Search Dropbox for files and folders by name or content. Returns matching paths, file types, and metadata. Use when you need to find a file without knowing its exact location. |
dropbox_get_metadata | Get detailed metadata for a file or folder: size, modified date, ID, sharing status, and revision info. Use before downloading or modifying to inspect properties. |
dropbox_download | Download a file from Dropbox and return its content as text plus metadata (size, type, modified date). Use to retrieve file contents for processing or inspection. |
dropbox_create_folder | Create a new folder in Dropbox at a specified path. Returns folder metadata. Use to organize files or set up directory structures. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dropbox": {
"url": "https://gateway.pipeworx.io/dropbox/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/dropbox/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1878+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack runs against a connected dropbox account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect dropbox, then call POST https://gateway.pipeworx.io/v1/tools/dropbox_list_folder with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/dropbox_list_folder. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"dropbox": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-dropbox"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-dropbox
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Dropbox data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.