Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http dropbox 'https://gateway.pipeworx.io/dropbox/mcp'{
"mcpServers": {
"dropbox": {
"type": "http",
"url": "https://gateway.pipeworx.io/dropbox/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-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-dropboxIt 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
Questions fréquentes
Qu'est-ce que Dropbox ?
Dropbox MCP Pack — wraps the Dropbox API v2
Comment installer Dropbox ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http dropbox 'https://gateway.pipeworx.io/dropbox/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Dropbox ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Dropbox est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Dropbox ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.