dbx

dbx-mcp-server exposes Dropbox capabilities to MCP-compatible clients via a set of tools. After configuring your MCP client to point at this server (for example using the provided build/index.js path in your MCP settings), you can execute operations such as listing files, uploading or downloading content, creating folders, and generating sharing links through the server's tool surface. The available actions map to Dropbox API permissions and are invoked by name (for example, list_files, upload_file, download_file, get_file_metadata, get_sharing_link, and get_account_info). Each tool accepts a structured payload, enabling you to pass paths, file contents (as base64, when needed), and query parameters. The server handles OAuth 2.0 with PKCE to secure access to your Dropbox resources, refreshing tokens as configured by environment variables. When integrating, ensure your MCP client requests the appropriate scopes to match the actions you perform (e.g., files.metadata.read for listing or get_file_metadata, files.content.write for uploads).

Prerequisites:

• Node.js and npm installed on the host where you will run the MCP server
• A Dropbox developer app configured with the required scopes and a registered redirect URI
• Access to edit your MCP settings to register the server

Installation steps:

1. Clone the repository git clone https://github.com/your-username/dbx-mcp-server.git cd dbx-mcp-server

2. Install dependencies and build npm install npm run build

3. Run setup (initialization and OAuth flow) npm run setup

4. Configure MCP to use the server (example) // In your MCP settings, reference the built server entry { "mcpServers": { "dbx": { "command": "node", "args": ["/path/to/dbx-mcp-server/build/index.js"] } } }

Prerequisites reminder:

• Ensure DROPBOX_APP_KEY, DROPBOX_APP_SECRET, and DROPBOX_REDIRECT_URI are properly set in your environment to enable OAuth PKCE authentication.
• Provide a TOKEN_ENCRYPTION_KEY for token encryption as described in the environment variables section.

Tips and common issues:

• Make sure the Dropbox app permissions align with the actions you intend to perform (e.g., files.metadata.read for listing, files.content.write for uploads).
• If token refresh fails, verify that TOKEN_ENCRYPTION_KEY is correctly configured and that network access to Dropbox is available.
• Use the provided environment variable placeholders to document required keys in your deployment environment and consider tooling to inject secrets securely.
• When testing, start with non-destructive actions (list_files, get_account_info, get_file_metadata) before attempting write operations like upload_file or delete actions.