Dropbox by CData

What it is

A local, read-only MCP server that exposes Dropbox as a relational SQL model. It wraps CData's JDBC driver for Dropbox, which presents the account's files, folders and metadata as tables, so an assistant can discover the schema and answer questions with live SELECT queries.

What you get

• The tables available in Dropbox, returned as CSV with a header row — get_tables
• The columns on a chosen table, so a query targets real column names — get_columns
• A SQL SELECT executed against live Dropbox data — run_query
• Tool names prefixed with the server name from your properties file, so several CData servers can coexist in one client
• A Tables setting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with

Requirements

A Dropbox account, plus CData's JDBC driver for Dropbox downloaded and licensed separately — java -jar cdata.jdbc.dropbox.jar --license takes your name, email and TRIAL or a license key. Java and Maven: mvn clean install produces the runnable JAR. Then a .prp file with the prefix, server name and version, the driver JAR path, the driver class cdata.jdbc.dropbox.DropboxDriver, and the JDBC connection string from the driver's connection-string utility — since Dropbox uses OAuth, that utility opens a browser to authenticate. The client entry runs java with the JAR and the .prp path. Communication is over stdio, so client and server must be on the same machine. MIT licensed.

Setup effort

Build from source — clone the repository, then point your client at the binary

Tools you get

3 tools named in the project's documentation. Tool names take the server name from your config file, as {servername}_get_tables, {servername}_get_columns and {servername}_run_query. The server is read-only (SELECT only), and files appear as metadata rows, not contents.

Where it runs

The documented client runs the server on your machine.